“When will we be paid?” — answered before it's asked.

Invoice status with block reasons, due dates computed from the terms, and the true landed cost of every order.

What finance gets

• One invoice vocabulary. Awaiting invoice → received, processing → blocked (reason, whose move) → approved, pays on date → paid, reference. The same words for the buyer, the supplier and the ERP.
• Due dates before the ERP posts. “70% T/T against B/L copy, Net 60” becomes a date the moment the B/L arrives.
• Blocked invoices with the fix. “Invoice 10,000 kg vs received 9,900 kg; a credit note for 100 kg releases payment.” The supplier sees the same sentence.
• Method-aware pages. T/T advance gates, L/C expiry and latest-shipment warnings, D/P documents-against-payment reminders.
• Cost lines per order. Freight, insurance, duties, brokerage, demurrage, bank charges, claims — with source and status, rolled up to landed cost per unit.

What stops happening

Suppliers emailing three people to ask about one invoice. Procurement forwarding those emails to AP. AP looking it up in the ERP and typing the answer back. Everyone doing it again next month.

Related

• T/T vs L/C vs D/P
• Computing due dates from the B/L date
• Payment due date calculator
• For suppliers