Accounts payable & receivable
Bills arrive by email and land coded. Approvals split so no one person can redirect a payment and release it. Every bill is checked against what was actually agreed. Then your own bank moves the money.
Netterms never holds funds. No money transmitter licence, because none is needed.
A bill you owe, an invoice you raise, a carrier settlement and an expense receipt are the same object seen from different sides. Netterms models it once — so coding, approval, matching and settlement work identically no matter which one you are looking at.
Vendors email a PDF to your intake address and it appears in the review queue. They change nothing about how they invoice you.
Read, coded, matched against the purchase order or load it belongs to, and routed for approval. A bill billed above what was agreed is flagged before anyone signs it.
Approved bills go into a payment run that produces an ACH file. You upload it to your bank. Nothing settles until you confirm the money actually left.
AP fraud is rarely a stolen password. It is one person who can add a vendor, change its bank details, approve a bill and release the payment. Those are four separate permissions here, and no role but Owner holds all of them.
A bill for $2,400 against a load agreed at $1,900 is flagged before approval, not discovered at month end. Tolerances are dual — a difference must exceed both a percentage and an amount — so the exception queue stays readable.
A request to update remit-to details almost always arrives by email. Changing them needs its own permission, resets the account to unverified, and is audited with the old and new last four.
When a carrier factors its invoices, a Notice of Assignment binds payment to the factor. Pay the carrier instead and you can be made to pay twice. Netterms redirects the payee automatically and says so on the payment run.
The first reminder goes out before the invoice is late, which collects more than anything sent after. An open dispute pauses the sequence entirely — chasing someone who already told you what is wrong is worse than silence.
A trip is one claim with one line per receipt, so it approves once and reimburses as a single payment rather than sixteen. An approver sees at a glance which lines have no receipt behind them.
Your books live in an accounting system and your work lives in an operational one. Netterms sits between them: pulling the chart of accounts and the counterparties from one, and what was agreed and delivered from the other.
Each is registered with its transport and documentation recorded — so “do you integrate with X?” has a real answer rather than a sales guess.
Netterms never takes custody of your funds. A payment run produces an instruction — a NACHA file for your bank, a positive-pay file, or a bill pushed to QuickBooks bill pay — and your bank executes it.
That is a deliberate design decision, not a missing feature. No money transmitter licensing, no settlement risk, and no third party sitting between you and a vendor waiting to be paid.
Flat monthly tiers metered on documents, never on people.
$49 / 100 a month, $129 / 500, $299 / 2,000,
and a conversation above that.
Unlimited users on every tier. Charging per approver taxes exactly the people you need in the system and quietly pushes teams into sharing logins — which destroys the audit trail the software exists to keep. No setup fee, no percentage of what you pay out, no charge per counterparty.
Netterms is being rolled out to its first users, so accounts are set up by hand rather than through a sign-up form. Say what you run today and what your month end looks like, and you will get a straight answer about whether it fits.
slavikp91@gmail.com