Post Transactions

When you post transactions, the system creates open invoices for each invoice or shipped order and miscellaneous credit entry that you recorded as a transaction. Next, the system updates both the due date for each transaction using the invoice date and the number of due days for the terms code and the discount date from the invoice date and the number of discount days from the same terms code. Finally, the system creates a payment record for each cash receipt. Posting ignores transaction entries that have a status of Backordered, New, Picked, RMA, or Price Quote.

As you post information, line-item information is posted first, then totals are updated. When all line items are posted, cash receipts information is posted, and finally detail and summary GL entries are created and posted. Payments are posted in the Accounts Receivable Post Cash Receipts function.

If you interface Sales Order with General Ledger, debit and credit entries are created in the GL journal for each line item. If you post only summary information to General Ledger, the transaction figures are summarized into one entry for each account. If the accounting period is closed, you can either edit the transactions or use the System Manager Period Conversion function to open the accounting period and then post the transactions.

Posting also updates customer, sales representative, and tax location records. The balance and the sales payment history fields in the customer's records are updated. The period-to-date, quarter-to-date, and year-to-date gross sales figures for sales representatives are updated. The taxable and nontaxable totals from the transactions update the totals of the tax locations in System Manager.

Traverse automatically creates entries for any realized gains or losses due to fluctuating currency exchange rates for payments in the accounts you specified in the System Manager Gains and Losses Accounts setup when you post to record those gains and losses for correct accounting.

Commission detail is updated if you elected to keep sales commission detail in the Business Rules function.

If orders contain any backordered line-item, the backordered quantity becomes the order quantity and the transaction order status changes to 'Backordered'.

Posting Transactions

  1. Complete transaction entry.
  2. Print invoices.
  3. Print the transaction journals.
  4. Select the Do the following then check the box check box.
  5. If you use multicurrency, select the Print Log Using Base Currency check box to print the log using your base, or functional, currency. When this check box is clear, the log includes posted values organized by currency along with their base currency equivalents.

  6. Select the batches to post. This option only appears if you elected to use batch processing in the Business Rules function. You can use the All button to select all batches to post.
  7. Select whether to leave unposted orders and backorders in their current batch or move them to a new batch from the Unposted Orders and Backorders section.
    Note: If you select Move to New Batch, you must select a new batch code from the New Batch Code field.
  8. Enter comments for the post, if applicable, in the Comments field.
  9. Click a command button to  
  10. Click To
    OK Post the transactions.
    Activity Display the Activity Log to view posting activity.
    Reset Set all fields to their default values.

In the Avalara tax transaction processing workflow, various tax statuses dictate the handling of transactions, influencing whether they are posted and committed to Avalara.

Transactions labeled with the tax status Tax Calculated will be both posted and committed to Avalara. However, if the Avalara tax calculation is inaccurate or if transactions are marked with the tax status Recalculate Tax, they will be held from posting or commitment to Avalara until the tax calculation issues are resolved.

For transactions indicating a tax status of None, posting will occur, but they will not be pushed to Avalara since the tax calculation is handled internally. It's essential to review and correct any transactions with inaccurate tax calculations to ensure compliance and accurate financial reporting.

Additionally, transactions that are saved and subsequently deleted after Avalara Tax calculation will be voided in the Avalara portal following subsequent post transactions.

After transactions are posted and committed, the TS Commit field in the history table will be updated. This can be viewed in both the AR Detail History View and the AR Transaction History View.