Sage 50 UK Payment Allocation XML
The allocate payments task allows you to allocate existing transactions in Sage 50. We recommend that the Id field be populated by the unique id of the allocations from the external system, Zynk uses this field to track allocations already imported to prevent duplicates being created in Sage.
Tasks
XML
Any Sage 50 fields not documented below are not supported with our imports / exports. Examples of where in the XML the fields should appear are shown in the samples below.
<?xml version="1.0"?>
<Company>
<PaymentAllocations>
<PaymentAllocation>
<CreditNumber>21</CreditNumber>
<InvoiceNumber>20</InvoiceNumber>
<Amount>14.80</Amount>
</PaymentAllocation>
</PaymentAllocations>
</Company>
In each of the following sections most of the XML has been omitted to make the samples easier to read. The whole structure of the Company schema is used below as a reference of where fields should be in the object model.
Details
The two transactions to allocate are identified by the transaction number displayed in Sage 50. Ensure that the credit transaction (i.e. a transaction of type SA, SC, SR, PA, PC or PR) is specified via the CreditNumber field in the XML, and the debit transaction (i.e. a transaction of type SI, SP, PI or PP) is specified via the InvoiceNumber.
| Sage Field | XML Field | Example | Field Type | Field Length | Input | Notes |
|---|---|---|---|---|---|---|
| No | CreditNumber | 21 | int | - | Required | The transaction number of the credit transaction (i.e. a transaction of type SA, SC, SR, PA, PC or PR) |
| No | InvoiceNumber | 20 | int | - | Required | The transaction number of the debit transaction (i.e. a transaction of type SI, SP, PI or PP) |
| Amount | Amount | 14.80 | decimal | - | Optional | If not specified, the task will allocate the maximum amount possible |