Siigo payment voucher posting

Purpose

Turn a payment described in plain words ("cliente 900123456 pagó la factura FV-1-1234, 1.190.000 por transferencia") into a correctly posted document in Siigo Nube. The skill checks every reference against Siigo and against the imported chart of accounts before it posts, so that the document lands with the right third party, document type, payment method, cost center and account codes on the first attempt.

Scope

The work covers three document families: Recibo de Caja for money received from a customer, Comprobante de Egreso for money paid to a supplier, and Comprobante contable for free journal entries such as adjustments or advance crossings. It handles debt payments against open installments, advances without an invoice, and detailed account lines that must balance.

Excluded: purchase or sales invoices, cancelling or editing a document that already exists in Siigo, and creating third parties with address data that was not provided.

Data basis

• The payment description from the input: who paid or was paid, amount, date, payment method, invoice references, purpose.
• Siigo catalogs through the integration: document types, payment types, cost centers, misc incomes, the customer lookup and the open accounts payable of a supplier.
• The siigo_cuentas record type in scope, searched with search_records on codigo and nombre to find the postable eight-digit accounts.

Result

One posted Siigo document with its returned number and name (for example RC-1-1234), and a posting log that lists every resolved value, the request that was sent and the answer from Siigo, or the reason why nothing was posted.

Quality criteria

• The third party exists in Siigo (customer:find returns found) before any document is posted.
• Amounts are exact to the cent; the sum of dues equals the payment value and debits equal credits in detailed lines.
• Only eight-digit account codes from siigo_cuentas are used; accounts marked "Con vencimiento" always carry a due reference.
• A Siigo error is corrected and re-posted at most once; a duplicated_document error is reported, never re-posted.

Instructions

Read the payment description and decide the family: money in from a customer means cashReceipt, money out to a supplier means paymentReceipt, anything else is a journal entry. Look up the third party with customer:find using digits only; if it is not found, stop and report. Use the pinned document type and payment type when they are set; otherwise take active entries from catalog:listDocumentTypes and catalog:listPaymentTypes and explain the choice. When the document type demands a cost center, choose one from catalog:listCostCenters. For a debt payment on the supplier side, fetch the open installments with accountsPayable:list and copy prefix, consecutive, quote and date exactly; on the customer side take the invoice reference from the description. For journal entries and detailed receipts, search siigo_cuentas with a codigo or nombre filter and pick eight-digit accounts only; add a due block whenever maneja_vencimientos says "Con vencimiento". Write amounts with two decimals and make dues sum to the value. Post once; if Siigo rejects the request, read the code and params in the error, fix that field and post again, but never post a third time. If the answer is a timeout, a server error or duplicated_document, report that the outcome in Siigo is unknown and ask for a manual check. Write the posting log with all resolved identifiers.

Adapt before use

• Select the Siigo credential and pin document type and payment type for the receipt operations; leave the pinned receipt type at DebtPayment or change it to AdvancePayment when the skill handles advances.
• Add the Siigo chart of accounts record type to the skill scope after importing it.
• Test against a Siigo test tenant before pointing the credential at production.