An invoice is accepted, but the money has not arrived. In another sale, the processor confirmed payment while fiscal transmission has a problem. Both can happen because payment and fiscal validation answer different questions. You need to know the outstanding amount and what happened to the electronic document. Treating one label as a complete sale summary can cause unjustified collection calls, duplicate records, or a second charge to the customer.
What fiscal status tells you
Hacienda's official API documentation distinguishes received, processing, accepted, rejected, and error states. It explains that initial receipt leaves validation pending. A received request therefore does not yet establish acceptance. Inspect the response linked to the document and its key when investigating an incident. These distinctions come from the official source below, not from email delivery or a customer's statement that they paid.
In Tario, inspect the document's fiscal status and current transmission. After attempts or corrections, an old response may describe an earlier version. Compare the response key with the document under review rather than using an old file to override the current conclusion. Keep the history to explain what happened, but use the current document for operational decisions. A screenshot may omit that version difference.
What payment status tells you
Payment tracking concerns original amount, linked payments, and outstanding balance. A CRC450,000 invoice with a CRC150,000 payment still has CRC300,000 to collect even if Hacienda accepted it. Its due date helps determine whether that balance is overdue. Check currency and allocation: receiving a transfer does not establish that it has been assigned to this particular invoice.
Tario supports recording full or partial payments and linking existing movements through the applicable workflow. If a deposit was already imported, check that option before creating another record. Incorrect allocation can make documents appear paid by the wrong deposit or leave money unapplied while collections contacts the customer. The bank evidence, movement, and invoice association should describe the same transaction.
Read the dimensions together
- Accepted and unpaid: review due date and collection follow-up; fiscal acceptance does not record a deposit.
- Accepted and partially paid: verify payments and request only the relevant remaining balance.
- Fiscal response pending: inspect transmission and response before concluding that acceptance occurred.
- Confirmed charge with a fiscal incident: preserve the payment and investigate the document without charging again.
Imagine a credit sale delivered on Monday. The invoice is accepted that day and due thirty days later. On Tuesday it may remain unpaid while being within agreed terms. Another invoice from the same customer has a partial payment and is ten days overdue. Acceptance alone cannot order collection priorities. Collections needs due dates, balances, and agreements; fiscal review needs documents and responses even when the balance is zero.
A fiscal problem does not authorize another charge
At a point of sale, verify payment outcome separately from document outcome. If the processor confirmed the operation, a later fiscal failure does not make that money disappear. Do not charge again merely to turn every indicator green. Identify the original payment, order, and document, then follow fiscal review. Any appropriate refund also needs its own decision and procedure.
This matters when a customer shows a card charge but the employee sees only an incident on screen. Locate the processor result first and avoid repetition. Then determine whether the document issue concerns sending, waiting, or the fiscal response. Request help using transaction identifiers, not credentials or full card details. Fixing documentation does not require blindly repeating the financial operation.
Investigate balance differences with dates
A customer may have paid near bank closing while your morning query still shows an outstanding amount. Other differences arise from incorrect references or allocation to an earlier invoice. Compare effective date, amount, and linked document. If several invoices share the same amount, do not select the first match without evidence. Check the customer's payment instruction or accompanying invoice list.
Adjustments and refunds need separate attention. A correction reducing a balance does not establish cash receipt, and a bank refund alone does not explain its documentary treatment. Separate payments from adjustments when reporting monthly collections. Align cutoff, currency, and included documents if reports disagree. Do not edit an amount simply to match a screenshot of a bank balance.
Assign owners and retain evidence
One person may review both dimensions in a small team, but keep two questions: what happened to the document, and what happened to the money? Record an owner, next step, and evidence for each incident. Accounting may need the fiscal response, collections needs the balance and payment promise, and payment support needs the transaction reference. A note saying bad invoice gives none of them enough information.
Before closing a case, confirm that current status, files, and linked payments explain the resolution. Resending an invoice changes neither payment nor Hacienda's response. If AI prepared a proposed action, manual issuance still requires explicit confirmation. Keep a concrete review note and avoid claims of automatic payment: software displays records, while your team must verify the operation it is authorizing.