Account Transactions

Workflows > Endpoints > Reporting > Account Transactions

Purpose: Retrieve the accoount transactions from the client, within a given date interval.

This endpoint is typically used in cases for detailed accounting reporting. What you retreive with the related endpoint trial balance, is a list of the general ledger accounts from the client and the current aggregated balance of these accounts. If transaction details are needed, this endpoint, Account Transactions, can be used to retreive this. The trial balances are simply the aggregated sum of the account transactions.

A common workflow for integrated applications that need to retreive all account transactions, is to start off by retreiving the starting trial balance, and then using only the account transactions from then on to provide flexibility with the reporting. The starting balance is the trial balance imported to Go when the client first started using Go as the accounting system. The Account Setting endpoint for fianancial settings, will provide information on the conversion date, which is the relevant date for retreiving the starting trial balance.

Assuming you store the data, after retreiving the initial account transactions we recommend a setup where you only query for and retreive new transactions from the client. Only the description field can be changed on vouchers already posted in Go. Any other change that involve a change of the accounting information, will automatically generate a reversal voucher (reversing the original) and a new voucher with the corrections made. For all practical purposes, the best way of retreiving new accounttransactions will then be to use a broad date range, and filter on voucher number > "the last registered voucher number you have". This will ensure that you always retreive all new vouchers with their transactions, depending on the page size. Filtering on created date > "your last registered created date" is also an option providing the same result.

If do you want to retreive any changes as well (description changes), the last changed property can be used for filtering, and you can then update the your registred description for any retreived account transactions already registrered from previous requests.

For subledger accounts (customer or supplier ledgers, typically connected with the accounts 1500 and 2400), account transactions will provide the transaction details, but it might be more relevant to retreive full subledger spesifications from the customer ledger or supplier ledger endpoints.

Endpoint

Descriptions

Retreive account transactions and poll on new transactions:

  1. Retreive the starting trial balance at the relevant date of choice (date inclusive), to provide a starting point

  2. Retreive all acccount transactions between the starting point and a date of choice

  3. From then on, poll on new account transactions using filtering

Prerequisites

  • Access to the AccountTrnsactions access privelige

    • The client need an active subscription of an accounting module of PowerOffice Go

  • Access to the TrialBalance access privelige (if needed)

    • The client need an active subscription of an accounting module of PowerOffice Go

Related workflows:

  • Accoount Transactions

  • Customer Ledger

  • Supplier Ledger

  • Dimension endpoints to supplement information

  • Contact endpoints to supplement information

Dictionary/Terminology

  • General ledger account: In accounting terms, this is an ordinary account used in the general ledger of the accounting system

  • Trial balance: A list of the aggregated sum of each account, at a given date

  • Account transaction: A singular transaction posted on a given general ledger account. A posted voucher allways consist of at least two account transactions, one debit (positive) and one credit (negative) - allways balancing to zero.

  • Subledger: A subset of a general ledger account, containing spesifications of the transactions for either customers, suppliers or employees. In PowerOffice Go, a general ledger acccount that have a subledger, require the use of the subledger account number (ie the customer/supplier/employee number) when transactions are posted.