Automatically pull incoming e-invoices from Uyumsoft, offset advances and credit notes to calculate the exact net amount payable, catch duplicate payments, and see each company's monthly payment budget in real time. Once the Finance → Purchasing → General Manager approval chain is complete, the bank payment instruction letter is generated with a single click. The ERP holds the invoice; the portal runs this multi-party pay/defer negotiation.
Logo, Mikro, SAP, Netsis or Uyumsoft keep the invoice and the supplier account as the single source of truth. But questions like 'which invoice do we pay on which date', 'did Purchasing push it back by a week', 'how much headroom is left against this month's budget ceiling' and 'is this invoice being paid a second time' have no answer in the ERP. These are a multi-party negotiation running over email and phone between Finance, Purchasing and the General Manager, kept in a single-owner Excel file. Customising the ERP to hold this deferral history, a live budget bar, duplicate-payment protection and list-based GM approval carries an unbearable cost. The portal builds this layer on top of the ERP and writes the approved result back to it.
e-Invoices and e-archive invoices are pulled automatically from the Uyumsoft API together with their GİB status; the supplier record is matched by tax ID, and each item is converted from the inbox into a draft invoice with a single click. Manual entry into Excel is over.
Advances paid and credit notes are automatically offset against the related invoice. The screen shows gross, offset and net amounts separately, so no one calculates the net payable by hand.
Matching on supplier + supplier invoice number + amount, combined with e-invoice UUID uniqueness, prevents the same invoice from entering the payment list a second time. Suspicious matches are flagged with a warning badge on the row and cannot be added to the list until resolved.
A budget bar at the top of the payment list shows paid + selected-in-this-list + remaining limit in real time. Each invoice selected is deducted from the budget of its planned payment month; if the limit is exceeded the row cannot be added, and the system routes you to a budget revision request.
The 'Defer' action requires a new date and a mandatory justification, notifies the counterparty, and logs every change with a who-did-what-when note. A payment can be deferred at most 3 times; after that the date can only be brought forward. The email back-and-forth ends.
The payment list moves through the Finance approver, Purchasing reconciliation and General Manager (final) steps on a list basis rather than invoice by invoice. The authority to change payment dates is bound at step level to the GM step only.
Once General Manager approval is complete, 'Generate Bank Instruction Letter' becomes active; the supplier IBAN is pulled from the Uyumsoft account record to produce a bank-specific PDF instruction and a period-based Invoice Payment Detail List.
Invoice lines are compared against the purchase order and goods receipt; quantity mismatches, price differences, missing goods receipt or over-invoicing exceptions are flagged. An invoice cannot proceed to approval and payment until every open exception is resolved.
Every mutation is written to the audit log, including date changes, deferrals, offsets, approvals and instruction generation. Each invoice's order–contract–invoice relationship chain and transaction history can be traced from the row detail, taking the process out of a single-owner Excel file.
e-Invoices/e-archive invoices are pulled from the Uyumsoft API with their GİB status, or entered manually; if the invoice originates from Purchasing, the PO and contract links are established automatically and the lines are matched against goods receipt.
Advance and credit-note offsets are deducted to calculate the net payable amount. Duplicate payments are caught through supplier + invoice number + amount matching; if any exception is open, the invoice does not proceed.
Purchasing enters a payment request and proposed date against the approved invoice. The deferral action runs with a justification and notification; up to 3 deferrals are logged.
Approved payments are added to the period list; each row is deducted live from the company budget of its planned month. When the limit is exceeded, the row cannot be added.
The list passes through the Finance → Purchasing → General Manager chain; after GM approval a bank-specific PDF instruction and detail list are generated, and the result is written back to the ERP.
The module is built entirely around ERP integration; Uyumsoft (and Logo/Mikro/SAP/Netsis) remains the single source of truth. The portal reads in a federated way and writes the approved payment result back to the ERP.
e-Invoices/e-archive invoices, GİB status, the supplier account record and IBAN are retrieved automatically from the Uyumsoft API. An invoice whose GİB status is not 'validated' cannot be added to the payment list.
For foreign-currency invoices the rate is taken from Uyumsoft (the TCMB rate); the portal does not go to a second rate source, so no double records or inconsistencies arise.
The payment request, offsetting and GM-approved payment decision are created in the portal; the paid status and accounting posting data are transferred cleanly to the ERP/accounting. The invoice record remains the single source of truth in the ERP.
Invoice lines are three-way matched against purchase order and goods receipt data; warehouse stock information can be taken from the ERP (e.g. Oracle). This way the payment decision is verified against the actual delivery.
Tell us your ERP and your process. We’ll show how this module works and scope it into your subscription — no man-day, licence or setup fee.
Book a Demo →