The Remittance Management feature requires a .json file format in order to process a payment request.
What is JSON format file how to get this?
JSON is a standard text-based format for representing structured data and is commonly used for transmitting data in web applications.
This file could be exported by your ERP system, in the requested format to be able to be processed.
Jinius is already working with popular ERP providers to be able to offer this functionality through their systems. We are increasing this list as we grow. If you want to use the Remittance Management feature through Jinius, but your ERP system cannot offer this file structure, contact us providing your ERP vendor details. We will contact your ERP vendor and arrange what is needed to help you have this export functionality available in your ERP as soon as possible.
What is the required file for Remittance Management?
File contains the below details:
Field |
Sub Field |
Description |
Remittance Advice Id |
Unique number to identify batch file |
|
Number of Payments |
Total payments to process |
|
Total Amount |
Total payment amount |
|
Execution Date |
Define execution date for the payment |
|
Payments |
Remittance record defined by required fields for the payment |
|
Supplier |
||
Company Name |
Recipient's Company Name - as is written in company registration records |
|
Company TIN |
Recipient's Company Tax Identification Number/Code |
|
Company VAT |
Recipient's Company VAT |
|
Company Registration Number |
Recipient's Company Registration number |
|
|
Recipient email for contact |
|
Payment Details |
||
Debtor Details |
||
Account Number |
Bank account number which will be used to pay the specific payment record - currently only Bank of Cyprus accounts are supported. |
|
Creditor Details |
||
Creditor IBAN |
Recipient IBAN - any valid IBAN could be provided |
|
Creditor Beneficiary name |
Recipient Account Name |
|
Remittance Amount |
Total payment amount for the specific record |
|
Payment Reference Number |
Reference number - this will be used to be identified by recipient – reference number defined by user’s system |
|
Invoices |
||
Buyer Reference Number |
Invoice reference number based on user’s system |
|
Supplier Invoice Number |
Issued invoice number - as provided by the supplier |
|
Invoice Total Amount |
Invoice amount to be paid |
|
Invoice Discount Amount |
Invoice discount - just informative value - not used for sums |
|
Issue Date |
Invoice issue date - available for crosschecks within the platform for invoice validity - if invoice exists in the platform |
An example of file is as below:
{ "groupHeader": { "remittanceAdviceId": "111111", "creationDateTime": "2021-08-16T13:30:31.176Z", "executionDate": "2021-08-16", "numberOfPayments": 1, "totalAmount": 100.00 }, "payments": [ { "paymentDetails": { "debtorDetails": { "accountNumber": "2222222" }, "creditorDetails": { "iban": "string", "creditorName": "333333" }, "amount": 100.00, "paymentReference": "122222" }, "supplier": { "taxIdentificationNumber": "11111111A", "vatNumber": "11111111A ", "companyRegistrationNumber": "A111111 ", "companyName": "Company Ltd", "email": "companyemail@companyemail.com" }, "invoices": [ { "buyerReferenceNumber": "DE133333", "supplierInvoiceNumber": "Q1444444", "amount": 100.00, "discount": 0, "issueDate": "2021-08-16" } ] } ] } |