A bank transaction can carry two dates: the date it happened (the transaction date) and the date the bank posted it (the posted date). LedgerSync shows the posted date in its transaction list, but sends the transaction date to QuickBooks Online (QBO). When the bank posts a transaction a day or more after it happened, the two dates differ.

Which date you see where

• In LedgerSync: Bank Connections > Transactions lists each transaction by its Posted Date.
• In QBO: when LedgerSync adds a transaction from a MasterCard or MX connection to QBO, it uses the transaction date.

Card purchases and checks often post a few days after they happen, so their date in QBO can be earlier than the Posted Date you see in LedgerSync.

Pending transactions

LedgerSync does not send a pending transaction to QBO. It waits until the bank posts it and sends it on a later sync.

Checks and other delays in LS QBO Validation

A check is usually entered in QBO on the day it is written, but the bank statement shows the day it cleared, which can be weeks later. LS QBO Validation allows for this when it matches bank statement lines to QBO transactions. The amounts must be equal, and the dates may be up to:

• 21 days apart for a QBO check matched to a check line on the statement
• 4 days apart for most other transactions

If the check number on both sides matches, the dates do not need to be close. A transaction that LS QBO Validation cannot match shows as an exception, for example missing from the bank or missing from QBO.

Checking a flagged transaction

Each exception shows the date, description and amount from the bank statement and from QBO. Click Resolve to review it, then choose Accept or Archive. Use Undo to change your mind.

When you choose the close period, the statement panel lists the account's previous statements and shows the statement PDF, so you can check the dates. Update Close Period copies the statement's dates into the close period.

Need help?

If you can't explain a date difference, contact LedgerSync Support at support@ledgersync.com.