Skip to main content

Reports - Accounting Sage 300 Export Report

Written by Andy Hornbeak

The Sage 300 Export report shows general ledger entries that have been exported to Sage 300. It is a record of what was sent, which makes it the report to use when you need to prove that a batch transferred, or to work out why Sage and Sharper disagree.

This article assumes you already know the basics of the Sharper reporting module — the Name, Token, Subtotal, column picker, and filter fields. For a full walkthrough of the reporting form itself, see the Sharper Reporting Reference Guide. This article only covers what's specific to the Sage 300 Export report.


This Report Only Applies to Sage 300

Before anything else: this report is filtered to exports of type Sage 300 specifically. If your property posts to QuickBooks, or to no external accounting system at all, it will always be empty.

This report shows entries that have already been exported. It does not create an export, trigger one, or list entries waiting to go — it is a record of what has been sent. An empty report means either that no Sage 300 export has run, or that your property does not use Sage 300. To find entries that have not yet been exported, use the General Ledger report and filter on Is Exported = No.


Why This Report Matters

When two accounting systems hold the same figures, the difficult question is always which entries made it across. This report answers that directly, which makes it useful for:

  • Confirming a period's entries were exported before you close it in either system

  • Reconciling a difference between Sharper and Sage 300 by comparing what was actually sent

  • Checking the accounts and amounts that went across, rather than the ones you expected to

  • Establishing when an export ran, using the export document date


Building a Sage 300 Export Report

  1. Go to Reports → Accounting → Sage 300 Export in the left sidebar.

  2. If a shipped report is close to what you need, use the ⋯ menu → Copy first — shipped reports can only be edited by the Sharper team.

  3. Otherwise click + New and give it a Name, such as "Sage Export Audit."

  4. Add the columns below from the Available panel.

  5. Set Subtotal to Debit Amount or Credit Amount to prove a batch totals correctly.

  6. Turn on All Outlets if you export across the whole company.

  7. Click Save, then Get Report to set your date range and run it.


Recommended Columns

The column list is close to the General Ledger report's, with one addition specific to exporting:

Field

What It Shows

Export Doc Date

The date of the export document — the column that identifies which export batch an entry belongs to. Unique to this report.

Transaction Date

The accounting date of the underlying entry — what determines the period it belongs to in Sage

Created Date

When the entry was recorded in Sharper

Account Name, Account Number, Account Type

The account the entry posted to — check these match your Sage chart of accounts

Document Type, Document, Document Num

What produced the entry and its reference, for tracing a line back into Sharper

Ledger Num, Memo

The ledger reference and description carried across

Is Debit, Amount, Debit Amount, Credit Amount, Net Amount

The value columns. Use Debit Amount and Credit Amount for totals — subtotalling Amount across a mix of debits and credits produces a meaningless figure.

Customer Name, Cust Type

The customer behind the entry, where there is one

Product Name, Product SKU, Product Tax Code, Product Taxable

The product behind the entry and how it is taxed

User Display Name, User Email

The staff member whose action created the entry

Note: Unlike the General Ledger report, this one carries no reservation or booking columns — an exported entry is described in accounting terms rather than operational ones. If you need to trace a line back to a specific stay, take its Document Num and look it up on the General Ledger report instead.


Useful Filters

  • One export batch: Field Export Doc Date, set to the date of the export.

  • A period's exported entries: Field Transaction Date, operator Between, covering the period.

  • Proving a batch balances: filter to one Export Doc Date and subtotal Debit Amount and Credit Amount — they should agree.

  • One account's exported activity: Field Account Number, set to the account.

  • Tracing a single document: Field Document Num, set to the reference.

The most useful routine here is to run the General Ledger report filtered to Is Exported = No before closing a period, and this report afterwards to confirm what went across.

Did this answer your question?