A Receiver Message is the electronic response a Costa Rican business sends about a supplier document it received. The message can accept the document, accept it partially or reject it. That decision should not come from a blind rule. It records which purchase the business recognizes and carries information used when determining the IVA credit treatment.
The practical problem begins before the message is sent. Someone needs to confirm that the supplier is known, the purchase happened, the line items match what was delivered and the document belongs to the correct legal entity. If an XML reached the wrong inbox or names another company as the receiver, automation should not quietly move it into the accounting records.
What each response means
Full acceptance is used when the company recognizes the document on its stated terms and has determined how it will be treated. Partial acceptance applies when only part is recognized, perhaps because one line was not delivered or a difference needs correction. Rejection is for a document the company does not recognize or cannot accept because of a material problem. The company's accountant should assess the facts; the label on a button does not decide the tax effect by itself.
- Accepted: the purchase, amounts and connection to the business have been reviewed.
- Partially accepted: one portion is recognized while another needs an explanation or correction.
- Rejected: the document does not belong to the business, the transaction did not occur, or a difference prevents recognition.
- Pending: this is not a fourth official response, but it is a useful internal status while information is missing.
A decision tree that works in daily operations
Start with identity. The receiver identification number in the XML should match the company whose records are being reviewed. Next, confirm the transaction through a purchase order, contract, delivery record or the person who received the service. Only then compare currency, date, quantities, discounts, taxes and total. Keeping those questions separate prevents a document from looking correct merely because its arithmetic works.
Imagine a café receives one XML covering coffee, cups and an equipment repair. The coffee and cups arrived, but the repair was never performed. Accepting everything ignores the difference. Rejecting everything can remove two valid purchases from the conversation. Partial acceptance provides a way to record the recognized portion, provided the accounting team confirms the treatment and writes a useful explanation.
- Does the receiver ID match the company that made the purchase?
- Is there an order, contract, delivery or responsible person confirming the transaction?
- Do quantities, prices, currency and taxes match the agreement?
- Does every line have the same IVA treatment?
- Should the supplier issue a credit note or corrected invoice?
- Does the internal note explain the partial acceptance or rejection?
IVA needs its own review
A real business purchase does not automatically mean all of its IVA receives the same treatment. Economic activity, use of the item or service, proportionality and other conditions may affect the available credit. The message structure includes information for that classification. A system can make it easier to enter and review, while the company's accounting policy and professional judgment still determine the answer.
Keep a visible trail: original XML, PDF representation, Hacienda response, internal decision, reviewer and the resulting bill. At month end, that group tells a clearer story than a folder of long filenames. It also shows which documents are still waiting for information without forcing someone to reread an entire month's email.
How Tario organizes the work
Tario receives XML, PDF or ZIP files, identifies the company through the receiver ID and prepares a bill for review. The Reception Inbox separates capture from judgment. Structured XML data supplies the supplier, lines, taxes and totals, while the team confirms IVA treatment and the Receiver Message. With a large batch, that separation keeps speed from turning into automatic approval.
A sensible operating goal is that no supplier document reaches the close without a known state. It may be accepted, partially accepted, rejected or pending for a visible reason. It should not disappear between email, downloaded files and a spreadsheet understood by only one person.