Skip to main content

Overview

Managing invoice payments involves three key aspects:
  • Payment terms: When payment is expected
  • Payment tracking: Monitoring what’s been paid
  • Payment reconciliation: Matching payments to invoices

Payment terms

Payment terms define when an invoice must be paid. They consist of two components: a type and a days value.

Payment term types

NET

Payment due a fixed number of days from the invoice date.
Examples:
  • NET 30: Due 30 days from invoice date
  • NET 15: Due 15 days from invoice date
  • NET 60: Due 60 days from invoice date
Due date calculation:

END_OF_MONTH

Payment due a certain number of days after the end of the invoice month.
Examples:
  • END_OF_MONTH 30: Due the last day of the month of 30 days after
  • END_OF_MONTH 0: Due on the last day of the invoice month
  • END_OF_MONTH 45: Due the last day of the month of 45 days after
Due date calculation:

Setting payment terms

Payment terms can be set when creating an invoice:

Due date calculation

The due_date is automatically calculated when you finalize the invoice:
If no payment terms are specified, the due_date is not calculated and payment tracking will be less meaningful.

Payment status

Once finalized, invoices track payment status automatically:

open

Invoice is due but the due date hasn’t passed yet.

due

Invoice is past its due date and still unpaid.

Partially paid

An invoice that has received a partial payment keeps its open or due status until it is fully paid. Check amount_paid and amount_remaining:
Invoice is fully paid.

Attaching payments

Record payments received or made on an invoice. All amounts here are accounting amounts: integers in the currency’s smallest unit (5000 = 50.00 EUR).

Full payment

Mark an invoice as fully paid:
This marks the invoice as paid with:
  • Amount: Full amount_remaining
  • Payment date: Current date
  • No external reference

Partial payment or detailed record

Record a partial payment with specific amount:

Payment parameters

All these parameters must be nested into a transaction_data field. Transaction types:
  • payment: a payment made toward an invoice, for instance by card or PayPal
  • transfer: a movement of funds between accounts or entities, for instance a payout to a supplier
  • balance_adjustment: a customer’s existing cash balance applied to an invoice, reducing the amount due
transaction_data itself is optional: when it is omitted, Nocotax records a payment of the full amount_remaining.

Payment reconciliation

Reconciliation is the process of matching payments to invoices and ensuring balances are accurate.

Automatic reconciliation

When you attach a payment, Nocotax automatically:
  1. Updates amount_remaining: Deducts payment amount
  2. Updates payment_status: Changes to paid once amount_remaining reaches 0. While a balance remains, the status stays open or due
  3. Adjusts AP/AR balances: Updates organization balances
  4. Records payment history: Tracks all payments on the invoice

Multiple payments

An invoice can have multiple payments:

Credit notes and payment balance

Credit notes affect the payment balance:
The credit note creates a credit balance that can be:
  • Refunded to the customer
  • Applied to future invoices
  • Tracked as credit owed
See Credit Notes for details.

Best practices

  • Always set payment terms when creating invoices for accurate due date tracking
  • Use NET terms for fixed payment periods
  • Use END_OF_MONTH terms for B2B customers who process payments monthly
  • Include payment references to link to external payment systems
  • Record partial payments as they’re received
  • Monitor payment_status to identify overdue invoices