One Person, Two Ledgers: Netting Input Credit Against a Produce Payment
A co-op member you sell fertiliser to and buy maize from is one person and two completely separate records — a customer with a receivable and a vendor with a payable. Nothing in the system knows they are the same human being. What it costs, the two instruments that get you most of the way, and what each of them writes to the ledger.
Every co-operative and every aggregator runs the same two-way relationship with the same person. You sell them inputs on credit in March. You buy their produce in September. In the accounts, one of those makes them a debtor and the other makes them a creditor, and in the yard they are just Mama Wanjiru with a receipt book.
The instinct is to net it: take what she owes for fertiliser off what you owe her for maize, pay the difference, and be done. That is exactly what a check-off is, and it is how this business has been run since long before anybody had software. The question this article answers is what actually happens when you try to do it in a system that stores the two sides in two unconnected places.
The two records, and why they never meet
A person you sell to is a customer: name, phone, currency, a credit limit, an opening balance, and invoices raised against them. A person you buy from is a vendor: name, phone, M-Pesa number or paybill, bank details, and payments made to them. Both are ordinary, well-built records. Neither carries a reference to the other.
That is not an oversight so much as a consequence of how the two halves of any business are usually shaped: your customers are rarely your suppliers. Agriculture is the exception, and it is the exception at scale — for a co-op, most counterparties are both. So the gap that a distributor would never notice is the one that defines your month-end.
What exists on each side of one member
Member as customer
A customer record with a credit limit and an opening balance you type. Invoices for inputs issued, aged and reported. An invoice that would push their exposure past the limit is held on credit hold with the amount it exceeded by, releasable by an override that records who overrode it and why. Statements, arrears and reminders all work from here.
Member as vendor
A vendor record with the payout details that matter in this market: M-Pesa phone for B2C, paybill or till for B2B, bank code and account. Payments to them are recorded in the Payments Register with a method, reference, amount and status, and appear in money-out reporting.
The link between them
There is no field on either record pointing at the other, no shared party identifier, and no screen that shows one person's receivable and payable side by side. You know they are the same person; the system does not, and no report will ever tell you.
Automatic netting on payment
Nothing deducts an outstanding input invoice from a produce payment. A payout pays what you tell it to pay. The deduction is arithmetic you do before you type the amount — and the record of why the amount was reduced lives wherever you choose to put it.
Member record, member number, produce ledger
Worth restating because it is the foundation the rest of this rests on: there is no member entity, no intake ticket, no grade, and no per-kilo calculation. This article is about the money once you know what it is, not about capturing the delivery — that gap is covered in member produce intake.
Read the pattern in the first two rows before the last three. The individual pieces are genuinely there and genuinely good; what is missing is that they know nothing about each other.
The credit note is the instrument you are looking for
A credit note reduces a customer invoice without cash moving. Issue one against Mama Wanjiru's fertiliser invoice for the value of the maize she delivered, apply it, and the receivable falls. That is a netting-off, recorded, numbered and dated, and it is the closest thing to a check-off that exists here.
It has a number of its own, a reason field, an issue date, an application date and three states — issued, applied, cancelled. An applied note cannot be cancelled, which is the right guard: once it has reduced a balance it is part of the record.
Found while writing this, and fixed
A credit note larger than the invoice balance used to apply what fitted and then close itself, discarding the difference in silence — a 5,000 note against a 2,000 balance credited 2,000 and destroyed 3,000. There is no column that holds a partly-consumed note, so the application is now refused with a message naming both figures. Issue a note for the amount you intend to credit, or apply it to an invoice with a balance large enough to absorb it.
What applying it does to the books
Here is the part to take to your accountant before the season starts. Applying a credit note posts a journal entry. It credits accounts receivable for the full value of the note, debits revenue back off the same income accounts the invoice credited and in the invoice's own proportions, and debits output tax by the invoice's own tax-to-total ratio. A foreign-currency invoice is reversed at the invoice's rate, so the note takes off exactly what the invoice put on. The entry carries the reference CN- plus the note number, and a retried request does not post it twice.
So the receivables control account falls with the invoice list, and the two agree. What the entry treats the netting as is a reduction of the sale, not a receipt of cash. Two consequences follow, and both are about how you read the figures rather than about anything missing from them.
- Revenue drops by the value you net. A season of heavy check-off shows lower sales of inputs than you invoiced, because the credit note is booked as a reversal of the sale. If your board wants gross input sales and produce purchases each shown in full, that is a presentation choice to settle with your accountant — a manual journal can reclassify it, and the credit-note list is the source for the figure.
- The invoice's paid amount includes the credit. Applying the note raises the invoice's paid figure and marks it credited or partly credited. Read cash collected from receipts and the Payments Register, which only cash reaches, rather than from the paid column on the invoice list.
One more thing the ledger cannot see: the produce side. The credit note settles the receivable, but the maize itself arrives as a vendor payment for the residue only — the 28,400 you netted never appears as a purchase. If you need the full value of produce bought, record it on the vendor side as well, and agree the treatment with your accountant once rather than every month.
The ledger hears about the credit note. It hears about it as a smaller sale, not as maize bought — so decide once how you want netting to read, and read cash from receipts.
What the month actually looks like
One member, one season, netted by hand
Illustrative figures. Three documents, two records, one person, and one treatment to agree with your accountant for the produce side. The arithmetic is trivial; the discipline is making sure the same three documents are produced every time, by everybody, in the same order.
The order matters more than you would think
Do it in the wrong sequence and you cannot reconstruct it later. Pay her the full 41,000 first and then chase the 28,400, and you have converted a settled account into a debt collection — which is precisely the outcome check-off exists to prevent.
The sequence that survives an audit is: value the delivery, credit the invoice, then pay the residue. Each step leaves a numbered document, and the payment reference carries the credit note number so the two sides can be tied together by a person, since no query will do it for you.
Put that reference discipline in writing before the season starts. A payment reference reading "September maize" is worthless six months later; one reading "CR-0184 net of inputs" reconstructs the whole transaction from either end.
The credit limit is the control you are not using
The input-credit failure mode is not usually theft. It is a member who has taken more inputs than their expected harvest can cover, agreed to informally, in three separate transactions, by three different people who each saw only their own.
A credit limit on the customer record turns that into a stop. Exposure is computed as the opening balance plus every open invoice, so the fourth request is held and flagged with the amount it would exceed by — visible, overridable, and with the override recorded against a name and a reason. That is not a per-member credit-scoring engine, which does not exist here. It is a ceiling and a paper trail, which is most of the value.
Set it from the acreage they have registered and the price you expect, then review it once a season. A limit nobody revises becomes a limit everybody overrides, and an override that happens every time has stopped being a control.
Questions to settle before the season, not during it
Who values the delivery, and against which price list?
What good looks like
One named role, one written price per grade per week, posted where members can see it.
If the answer is otherwise
A supplier contract can hold an agreed price per item for a set period, which suits a member on a contracted rate; a price that moves by grade every week is a posted list you keep yourself. If the price lives in somebody's head, the netting is a negotiation at the scale.
Who is allowed to issue a credit note?
What good looks like
A short list, separate from whoever values the delivery.
If the answer is otherwise
One person valuing and crediting is the whole control in one pair of hands. The permission is there — use it to split the two.
Where does the credit note number appear on the payout?
What good looks like
In the payment reference, every time, no exceptions.
If the answer is otherwise
Nothing links the payable and the receivable automatically. Without the reference the two halves are only connected by memory.
Who passes the netting total to the accountant, and when?
What good looks like
A named person, monthly, from the credit-note list.
If the answer is otherwise
Applied credit notes reach the ledger as reduced sales. The produce bought behind them does not, so the accountant needs the total to show purchases in full, if that is how you want the season to read.
What happens when the harvest is worth less than the inputs?
What good looks like
A written policy: carry it forward, or write it off, decided in advance.
If the answer is otherwise
There is no member debt account to carry a balance in, so the residue stays as an open customer invoice — which will start emailing them arrears reminders if they have an email address on file.
What we do and do not do
What AWRA OpsHub does today
- Customer and vendor records that each do their own job properly, including M-Pesa B2C payout details on the vendor side and a credit limit on the customer side.
- Credit notes — numbered, dated, reasoned, applied against a specific invoice, three states, and an applied note cannot be cancelled.
- A journal entry when a credit note is applied — receivable credited, revenue and output tax reversed in the invoice's own proportions and at its exchange rate, posted once.
- Credit-limit exposure with a hold and a recorded override, computed from the opening balance plus all open invoices.
- Customer statements you can filter by date and email out with your own subject and message.
- Overdue-invoice reminders to the customer, scheduled daily — and, from this batch, switchable off or slowed to weekly or monthly per organization, which previously ran ungated.
More we can add to your workspace
- A link between a customer and a vendor record. One person is two records and nothing joins them, in either direction, anywhere.
- Automatic netting or check-off. Every deduction is arithmetic you perform before typing an amount.
- A bulk member payout run. M-Pesa pays out — B2C to a phone, B2B to a paybill or till — one payment at a time, to a vendor.
- A member entity, produce intake, grading or per-kilo pricing. The value of the delivery is a figure you arrive at outside the system.
- Credit scoring, eligibility rules or seasonal credit cycle. A limit is a number you set and review; nothing derives it from history.
The customer-to-vendor link is the one that changes most: it is what would let a netting be one action instead of three documents. Everything in that column is visible work you know you are doing by hand, and each item is something we can add to your workspace.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsRunning it properly, in five decisions
- Register every member twice, deliberately — as a customer and as a vendor — with the same identifier in both names so a human can match them at a glance.
- Set a credit limit on every customer record before the input season opens, derived from acreage and expected price.
- Separate the person who values a delivery from the person who issues the credit note.
- Make the credit note number part of the payout reference, and audit ten payouts a month for it.
- Agree once with your accountant how netted produce should read — as a reduced sale, or reclassified as a purchase — and reconcile the receivables control account against the invoice list before you close.
None of that is exotic. It is the same discipline a co-op clerk with a ledger book and a carbon receipt has always run, which is worth saying plainly: the value here is that each step leaves a numbered, dated, attributable document instead of a line in a book only one person can read.
Our take
Netting a member's input credit against their produce payment is workable today with credit notes, and the paper trail is genuinely better than the receipt book it replaces. Applying the credit note reverses the receivable in the ledger as well as on the invoice. Two things are on you: deciding how netted produce should read in your accounts, since the ledger sees it as a smaller sale rather than a purchase, and the reference discipline that keeps the payable and the receivable connected, because nothing in the system knows they belong to the same person.
See customers, credit limits and statements
Credit limits with holds and recorded overrides, credit notes against invoices, statements you can email, and arrears reminders you control the cadence of.
Explore the customer viewFrequently asked questions
Can the system deduct what a member owes from what we pay them?
Not automatically. A customer record holds what they owe and a vendor record holds what you pay, and nothing joins the two — so the deduction is arithmetic you do before typing the payment amount. The instrument that records it properly is a credit note against their input invoice, which reduces the receivable without cash moving. Do that first, then pay the residue, and put the credit note number in the payment reference.
Why do we have to register a member twice?
Because the two sides of the relationship live in two different records with no link between them: a customer for what they buy from you, a vendor for what you buy from them. Use the same membership number in both names so a person can match them instantly, since no report will. It is duplication, it is visible, and it is the honest position rather than a hidden one.
Does applying a credit note appear in our accounts?
Yes. Applying a credit note posts a journal entry: accounts receivable is credited for the note, and revenue and output tax are debited back in the invoice's own proportions, at the invoice's exchange rate if it is in another currency. The receivables control account and the invoice list move together. What it records is a reduced sale rather than cash received, so read collections from receipts, and agree with your accountant whether netted produce should also be shown as a purchase.
What happens if a credit note is bigger than the invoice?
It is refused, with a message naming both figures. It used to apply what fitted and close itself, silently discarding the difference — there is no column for a partly-consumed note, so a partial application had nowhere to keep the residue. Issue a note for the amount you actually mean to credit, or apply it to an invoice with a balance large enough to absorb it.
Can we pay all our members in one run?
No. M-Pesa does pay out as well as in — B2C to a phone number, B2B to a paybill or till, with the transaction landing on the Payments Register — but it pays a vendor, one payment at a time. There is no bulk member payout run, no batch file and no payout schedule. At a few dozen members that is an afternoon; at several hundred it is the constraint that decides whether this fits your co-op.
How should we set a member's credit limit?
From their registered acreage and the price you expect, reviewed once a season. Exposure is computed as the opening balance you typed plus every open invoice, so the limit does real work: the request that breaches it is held and flagged with the excess amount, and the override records who released it and why. Nothing derives a limit from delivery history — there is no credit scoring — so it is a judgement you make and revisit deliberately.
Will a member with an unpaid input invoice be chased automatically?
Yes, if they have an email address on the customer record — an overdue-invoice reminder goes out on a schedule once the due date passes. That is worth knowing before you leave a residual balance open after a poor harvest: unless you change the setting, the reminder will keep going. The cadence and the on/off switch now sit with the other notification settings, which they did not before this batch.
