Transactions Report

Modified on Fri, Nov 21 at 8:07 AM

The Transaction report provides a listing of all transactions within the date range and dimension filters applied. With an API connection such as Sage Intacct, Martus will make a live request to pull up-to-date information into Martus when the transaction report loads. The transaction report is normally navigated to via link from another report and will apply the appropriate parameters, using the dimension restrictions of the user. If navigating directly to the report, select one or more filters and click Load.


How the Data is Pulled from Your Accounting System

When Martus loads the Transactions report via a link from another page, it automatically uses the parameters and dimension restrictions of the current user. This is best practice and produces expected results.


If you go directly to the Transactions report and hit Load, when we go to retrieve transactions, the user's restrictions and parameters are not applied, since they are normally encapsulated via the link. Martus must then query with a pretty broad query (in this case, it is only a date range), and then apply the user's restrictions after the transactions are returned.


We cap the total quantity of that first broad query at 1000. If no transactions are returned in the first grab that match the user's restrictions, Martus will respond with a yellow message, "Limit your selection filters to a shorter date range and/or a single account in order to find more matching transactions." If some transactions are returned that match, we go back and look at the next 1000, etc.


If the user filters specifically on a dimension or account before hitting Load, or drills down from a report like the Income Statement, where filters are already applied, that should produce the expected results.


ADDITIONAL NOTES: 

  • When you drilldown to the Transactions Report, income is shown as positive and expenses are shown as negative because it has to do the arithmetic. Otherwise, the total wouldn't make any sense.   
  • If the total of the selected transactions does not match the Income Statement, limit your selection filters to a shorter date range and/or a single account to find more matching transactions, as there is a maximum number of 1000 transactions that can be returned at one time.
  • If you notice that transaction amounts shown do not match those on the Income Statement, it is possible that transactions have been updated, but haven't synced with Martus. To resolve this, have an Admin user sync the necessary month(s) in Dashboard > Updater > Actuals.
  • Transactions cannot be updated in the Transactions report. Changes must be made in your accounting system.



Report Filters

  • Start and End Dates - Determines the date range for the transactions that are shown.
  • Include Excluded Data - Show accounts and/or dimensions that are set to Excluded via the Setup section.
  • Account - Specify the account to view.
  • Account Type- Specify the account types to view. Options include:
    • Income & Expense
    • Equity
    • Income, Expense & Equity
    • Stats
    • Asset & Liability - For API integrations only; non-admin users must have the Has Balance Sheet Reports permission.
  • Dimension Filters - When applied, these will filter the report to the selected dimension(s). When a top-level dimension is selected, the report will show all sub-dimensions.
  • Account Category - When applied, this will filter the report to the selected Account Category.
  • Load - Refreshes the report with selected criteria.
  • Export (xlsx) or PDF - Most reports can be exported to either Excel or PDF.


Attachments

Attachments can be viewed for specific integrations. Click on the paper clip to either view an associated attachment, or to launch the application where attachments are stored for your organization.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article