Define the invoicing handover before connecting the website

A fictional activity business has reservation R-017 for four people on a morning departure. The booking provider marks the reservation confirmed, but the staff screen has no issued-document reference. Those two states can both be true. The integration brief needs to say what accounting-related action, if any, should happen next; a developer should not infer it from the word confirmed.

Give the two records different jobs

Use R-017 as the operational reservation reference. Separately identify the provider-controlled document reference and its state. Do not fill an empty document field with the reservation number or show a generic success message as evidence of issuance. The staff view might accurately say that the reservation is confirmed while the document request still needs review.

Before implementation, the business's accountant and selected provider decide the applicable process: the event that authorizes a request, the required information and the person who approves it. This example does not decide when a document must be issued, which kind applies or how a cancellation must be handled.

Prepare an approved sample exchange

For the rehearsal, create invented reservation details and a sample document request using the provider's supported test method. Ask the responsible advisers to supply the relevant classification inputs, including any CABYS code and description they determine are appropriate. Do not choose a classification merely because a catalogue search result resembles the marketing name of the activity.

Banco Central de Costa Rica's CABYS catalogue information is an official starting point for the classification catalogue. It does not approve the classification for this fictional transaction or replace current accounting and provider instructions. Have the responsible people confirm the information against the process being implemented.

Lose the response after sending

Now let the test request leave the website but interrupt the reply before the staff screen receives a reference. The result is uncertain: a missing reply does not prove that nothing happened at the provider. Staff should see the reservation reference, the unresolved document action and a clear investigation route, without unnecessary personal details in diagnostic messages.

Use the provider's supported lookup or recovery method to determine the actual result before deciding whether another request is appropriate. Record how the returned reference is linked to R-017 and who resolves a result that cannot be matched. Do not assume every provider supports the same duplicate-prevention feature or retry procedure.

Change the reservation without rewriting history

Suppose the customer later asks for an afternoon departure. That is an operational change to review against availability. It should not silently replace the issued-document reference or cause a second document request just because the reservation record was saved again. The accountant and provider specify the separate document correction process where one is required.

Acceptance traces the original reservation, the uncertain request, the recovered result and the later date-change request. Ask a colleague to explain what is confirmed, what has been issued and what still needs action using only the agreed staff view. Include a provider rejection with a readable next step, rather than testing only the successful response.

Bring a reviewed record-flow sketch and provider name to a connection engagement. A bounded feasibility review can establish permitted access and supported operations before a wider automation is commissioned. Technical implementation does not certify tax compliance; retain the business's professional approval and keep real customer or identity records out of the initial public enquiry.