> ## Documentation Index > Fetch the complete documentation index at: https://help.vori.com/llms.txt > Use this file to discover all available pages before exploring further. # Errors, Retries, and Sync History > How Vori validates every entry before it posts, where each sync is recorded, and how to safely retry a failure. Because this data touches your financial records, you need full control and visibility over what hits your books and when. The governing principle: Vori holds a bad entry rather than forcing it through. A gap is easier to fix in Vori than to unpick in your accounting system later. *** ### What Vori catches before anything posts | Situation | What happens | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | A department or category has no account mapped | The push stops and shows each unmapped item with its amount. | | The day's debits and credits don't balance | Held and flagged, with the offending order named. Vori never posts an unbalanced entry. | | A bill's vendor isn't linked | The invoice can't be approved, so it never reaches your accounting system. | | A mapped account was deleted or made inactive | The push fails with the account named, rather than posting elsewhere. | | A store's segment value matches nothing in your accounting system | The entry posts, untagged for that store, and the mismatch is flagged in GL Code Mapping. | Because Vori re-reads your chart of accounts nightly, accounts you rename or add are picked up automatically, and anything that becomes unmapped as a result surfaces the same way. *** ### Sync history Every attempt is recorded. A sync history view under **Integrations → Accounting Sync** shows: * Timestamp, and who performed the action (a specific user, or Vori itself) * Type — daily journal entry, invoice bill, or chart-of-accounts pull * Reference — the business date, or the invoice number * Status — pending, success, or failed * The reference your accounting system returned on success, with a link to open the entry there * The specific error message on failure Failures are visible where you work. A journal entry or bill that fails to sync stays marked as unposted in Vori, with the error your accounting system returned. Failed bills are flagged in the **Invoice Review** queue so they aren't forgotten. *** ### Retries are safe Once you've fixed the underlying cause — added a missing mapping, reactivated an account, linked a vendor — retry the sync. Each push carries a stable reference to the underlying Vori record, so retrying a day or an invoice that already posted will not create a second copy. Every entry Vori posts is a discrete, referenced record, so there's a clear audit trail of exactly what posted and when. *** ### Frequently asked questions No. Vori doesn't create accounts and doesn't post to a default, catch-all, or suspense account. Posting against an account that doesn't exist, or a bill against a vendor with no counterpart, would create work instead of removing it, so incomplete mappings stop the push rather than routing around it. Not today. Bills are created in your accounting system and paid there, through whatever payment workflow you use now. Vori doesn't read payment status back, so AP aging and payment history live entirely in your accounting system. Nothing on Vori's side. Once an entry is in your accounting system it's that system's record, and Vori won't overwrite, re-post, or correct it. Vori doesn't read your posted transactions at all. Not today. The bill is created with the vendor, dates, terms, and coded lines. The source document stays viewable in Vori. Not today. Payroll stays in your payroll system and reaches your accounting system through its own integration. If you collect sales tax across several jurisdictions, each rate produces its own line on the daily entry, but all of them post to the same Tax Collected account. ## Related topics - [Accounting Integrations](/accounting-integrations/accounting-integrations-overview.md) - [Payment Terminal Error Messages](/point-of-sale-pos/basic-cashier-functions/payment-terminal-error-messages.md) - [Product History](/product-and-product-catalog-management/product-editing-and-activation/product-history.md)