Purchase Payments
Payments assigned to the Purchase Invoices we generate in Sage will be exported from Sage and converted to the Yooz payment feedback JSON data format. The resulting file will be uploaded to Yooz using the POST /feedbacks
API call.
Requirements & Assumptions/Assertions
- Payments will be transmitted to Yooz after they have been generated in the accounting system and assigned to a purchase invoice.
- The accounting systems permit partial payments to be assigned to a purchase invoice, hence there may be multiple payments associated with each Yooz purchase invoice or non-PO invoice.
- For instance, if there’s a purchase invoice for £10, with two payments of £6 and £4, we will transmit 2 payments to Yooz with the amounts £6 and £4.
- For Sage 50, any credit notes assigned to the purchase invoices we generate in Sage will also be treated in the same way as a payment.
- For instance, if there’s a purchase invoice for £10, with a £10 credit note assigned to it, we will transmit a £10 payment to Yooz.
- There is no requirement to generate separate JSON files for each organisation.
- The JSON file name format will be
{yyyyMMddHHmmssffff}.json
- The ‘yyyyMMddHHmmssffff’ is the timestamp format. An example of a file name will be, 202204191529002124.json
- The JSON files can contain multiple payment feedbacks. They will be output to the ‘documents’ array.
- If an invoice is generated in Sage by Zynk and then deleted, then generated again manually - Zynk will not be able to assign the payment to the original Yooz invoice.
Zynk Process
- Export purchase payments from the accounting system, where the allocation amount is greater than 0, and the purchase invoices they are associated with.
- Convert the Sage purchase payments to Yooz payment feedback JSON format.
- Upload the payment feedback JSON file to Yooz via the API.
Data Format
- The data will be in JSON format. A sample of the expected data format is shown below.
- The monetary amount format is 0.00
- The date format is yyyy-MM-dd, e.g. 2022-04-20
Example JSON Format
{
"documents": [
{
"yoozNumber": 15,
"action": {
"type": "PAYMENT",
"paymentDataItems": [
{
"code": "YZ_AMOUNT_PAID",
"value": 500.85
},
{
"code": "YZ_DATE_OF_PAYMENT",
"value": "2021-07-07"
}
]
}
}
]
}
Scheduling
The default schedule for this solution point is to run daily at midnight and 6am.
Field Mappings
Yooz Column | Yooz Column Description | Sage 50 Supplier Field |
---|---|---|
1 | Third party code | Details → A/C |
2 | Third party label | Details → Company Name |
3 | VAT number | Details → VAT Number |
4 | Phone Number | Details → Telephone |
5 | Fax Number | Details → Fax |
6 | Website | Details → Website |
7 | Address | Details → Street 1 |
8 | Address (line 2) | Details → Street 2 |
9 | Zip code | Details → Postcode |
10 | City | Details → Town |
11 | Country | Details → Country (2 char ISO code) |
12 | Contact name | Details → Contact name |
13 | Contact e-mail | Details → Email |
15 | Bank code | Bank → Sort code |
16 | Counter code | N/A, will be left blank |
17 | Bank account number | Bank → Account number |
18 | RIB key / Control Key | N/A, will be left blank |
19 | IBAN | N/A, will be left blank |
20 | Linked GL account | Defaults → Default Nominal Code |
21 | Company registration number | N/A, will be left blank |
22 | SIREN | N/A, will be left blank |
27 | Action | Will be set based on the Inactive checkbox - Not ticked → CREATE (to add/update a supplier), Ticked → DELETE (to deactivate an existing supplier) |