One account, every side of the farm
Open a working farm's bank statement and the deposits and withdrawals run together in one plain list, in whatever order the bank happens to post them. A grain settlement check sits two lines above a fertilizer payment. A government program payment from the Farm Service Agency lands the same week as a land rent payment going out. A crop insurance indemnity check looks, on the statement itself, exactly like any other deposit — nothing on the page says what it actually was.
None of that is a flaw in the statement. A bank statement was never built to tell a farm what its income and expenses actually were by category — it's a record of money moving, not a categorized ledger. Turning it into one means reading every line and deciding, transaction by transaction, what it represents: a crop sale, an input cost, a government payment, rent, equipment, or something personal that happened to run through the same account.
Why a farm statement doesn't sort itself
A settlement deposit is already net of several deductions
Drying, storage, checkoff assessments and sometimes freight are subtracted before a grain settlement check ever reaches the bank — the deposit is the last number in a chain, not a starting point.
Farm and household spending often share one account
On a family farming operation, groceries, a truck payment and a fertilizer bill can all clear the same account in the same week, with nothing on the statement itself distinguishing one from the other.
Income arrives in bursts, expenses arrive year-round
A season's worth of crop sales can land in a handful of deposits at harvest, while input costs, fuel and equipment payments are spread across twelve months — a shape that makes a simple monthly view misleading either way.
The same word means different things on different statements
"Coop payment," "ag payment," and a bank's own generic transfer code can each mean a settlement deposit, a patronage dividend, or an input purchase, depending entirely on which entity issued it.
None of these four are unusual or a sign of poor recordkeeping — they're the normal shape of how money moves through a working farm operation. They're also exactly why a bank statement, read on its own, rarely produces a confident category for every line without real effort.
What this doesn't do, stated up front
Doesn't file a Schedule F or any tax return
This gets income and expenses out of statements and into clean, categorized rows. Preparing and filing the return itself stays with your accountant or tax software.
Doesn't calculate depreciation or Section 179
Depreciation depends on elections and prior-year history this tool can't see. What it reads is the transaction as it appears on the statement — the equipment purchase or loan payment, not a depreciation schedule.
Doesn't connect to the FSA, RMA, or a crop insurance company
There's no login, no API, no integration with any government or insurance system. A program payment or indemnity check is read from the bank deposit itself, the same way any other deposit is.
Doesn't determine deferred grain contract tax treatment
Whether a settlement should be reported this year or next under a deferred-payment contract is a tax election your accountant makes — this reads the deposit as it hit the bank, on the date it hit the bank.
What's left is narrow, and it's exactly the part that eats an evening every time a lender, an accountant, or the end of the year makes it necessary: turning a stack of statements into clean, categorized numbers.
What gets read
| Field | Source |
|---|---|
| Deposit and withdrawal amount, date, description | Bank statement |
| Gross bushels, price, drying, storage, checkoff | Settlement statement |
| Input line items — seed, fertilizer, chemical, fuel | Supplier invoice |
| Government program payment reference | Bank statement |
| Running account balance | Bank statement |
Every field is read as it actually appears on the document — not summarized from memory, and not assumed to mean the same thing on every statement a farm produces.
How a farm transaction gets categorized
Categorization runs on the transaction description together with the amount and the pattern of similar transactions on the same statement — not a single keyword match, because a single keyword is too weak to trust on a document where the same short description can mean several different things depending on the farm.
| Category | Typical transaction |
|---|---|
| Crop or livestock sale | Elevator, co-op or buyer settlement deposit |
| Government payment | FSA program payment, conservation payment |
| Crop insurance | Indemnity payment, premium withdrawal |
| Input purchase | Seed, fertilizer, crop protection, fuel |
| Land and rent | Cash rent paid or received |
| Equipment | Purchase, loan payment, lease payment |
A transaction that fits cleanly into one of these gets categorized with high confidence. One that doesn't — a generic bank transfer with no useful description, or a transaction that could plausibly be either farm or household — is flagged for a quick manual confirm rather than guessed at silently.
A season, reconciled
A 500-acre wheat and soybean operation, one bank account, one harvest settlement, one fall input prepay.
| Line | Amount |
|---|---|
| Wheat settlement, 18,400 bu gross | $94,300 |
| Drying, storage, checkoff deducted | −$3,850 |
| Net settlement deposit | $90,450 |
| FSA program payment | $6,200 |
| Fall fertilizer and seed prepay | −$41,600 |
| Cash rent paid, three tracts | −$28,000 |
The $90,450 deposit on the bank statement, taken alone, gives no indication that 18,400 bushels sold at a plausible price for the year. Read alongside the settlement statement, the drying and storage deductions land in their own line, and the deposit is confirmed against gross bushels and price rather than accepted as a round number that looked about right.
How it works
Upload the bank statement, plus settlement statements and input invoices
Whatever the bank and elevator or co-op issue, plus supplier invoices covering the same period.
Every transaction is read
Date, amount, description and — where a settlement statement is included — the deduction breakdown behind a net deposit.
Categorized with a confidence level
Crop sale, input, government payment, rent, equipment or personal, with ambiguous lines flagged for review.
Export
Excel, CSV or JSON — one row per transaction, categorized and dated, ready to hand to an accountant or drop into a spreadsheet.
Reading a settlement statement alongside the bank
A grain elevator or co-op settlement statement carries detail a bank statement never will: gross bushels delivered, the price applied, dockage for moisture or foreign material, drying and storage charges, and any checkoff assessment withheld before the net figure is paid out. On its own, the bank deposit is just that net figure, with nothing to explain how it was reached.
Reading the two together closes that gap — the settlement statement's own breakdown is read as line items, and the bank deposit is confirmed against the net figure the statement says it should produce. The detail behind grain and livestock settlement specifically is covered further in crop settlement statement extraction.
Prepaid inputs and why timing matters
A common pattern on a row-crop operation is paying for next season's seed, fertilizer and chemical in the fall — often for cash-flow or price-lock reasons — well before any of it is applied to a field the following spring. On the bank statement, that shows up as a large withdrawal months before the crop it paid for is even planted, which can make a given month's numbers look far worse than the operation actually is.
Reading the transaction as it happened — a large input payment on a specific date, categorized as a prepaid input rather than folded silently into ordinary operating expense — keeps that timing visible instead of buried. What to do with a prepaid input for tax purposes is a question for your accountant; what this tool does is make sure the transaction itself is captured accurately and dated correctly, so that conversation starts from real numbers.
Government payments and crop insurance
A program payment from the Farm Service Agency and an indemnity payment from a crop insurance company both arrive as an ordinary-looking deposit, with a bank description that rarely says more than a generic reference code. Left uncategorized, both blend into the same pile as an ordinary crop sale — which makes it hard to answer a simple question like how much of this year's income actually came from crop sales versus support payments.
Where the description on the statement makes the source identifiable, the deposit is categorized separately — government payment or crop insurance, not crop sale — so that distinction survives into the export instead of disappearing into an undifferentiated income total.
More than one operation on one desk
A farm running a crop operation and a separate livestock operation — or a farming corporation alongside a family trust that owns the land — often has more than one bank account, and more than one set of statements to get through at the same time.
Each entity's statements are processed and kept as their own export rather than merged into one undifferentiated pile — a crop operation's categorized transactions stay separate from a livestock operation's, and each can be handed to an accountant, lender or partner as its own clean file.
Livestock sale settlements
A livestock operation's income arrives the same way a grain operation's does — as a net settlement deposit from a sale barn, packer, or direct buyer, with weight, price per hundredweight, and deductions for commission, yardage or trucking already subtracted before the bank ever sees the figure. Read on its own, a livestock settlement deposit is just as opaque as a grain one, and for the same reason: everything that explains it lives on a document the bank statement never carries.
Categorization treats a livestock settlement as its own category, distinct from crop sales, so that an operation running both a cow-calf herd and row crops can see each income stream on its own rather than folded into one undifferentiated sales total. Feed purchases, veterinary bills and breeding stock costs are read the same way on the expense side, categorized separately from crop input costs.
Co-op patronage dividends and equity redemptions
A farm marketing through a cooperative often receives two kinds of payment that aren't ordinary crop sales at all: a patronage dividend, paid out of the co-op's margins in proportion to how much business a member did with it, and an equity redemption, returning capital the co-op held on a member's behalf from prior years. Both typically show up on the bank statement looking identical to any other co-op deposit, usually with a Form 1099-PATR arriving separately at tax time to explain what actually happened.
Where the bank description or an accompanying co-op statement makes the payment type identifiable, it's categorized as patronage income or equity redemption rather than absorbed into ordinary settlement income — a distinction that matters because the two are often treated differently for tax purposes, and because conflating them with crop sales overstates how much of a year's income actually came from the crop itself.
Land rent, paid and received
An operation renting ground from a landlord, or renting some of its own ground out to a neighbor, sees both sides show up as ordinary bank transactions — a cash rent payment going out each fall, or a rent deposit coming in from a tenant. Categorized as land expense or land income respectively, these are kept distinct from operating input costs and crop sales, which matters for anyone trying to separate the economics of farming the ground from the economics of owning it.
A farm running several rented tracts under different landlords, at different per-acre rates and different payment dates, benefits most from this — instead of one lump land-rent total, each tract's payment is its own row, traceable back to which landlord and which parcel it belongs to.
Operating loan draws and payments
Many operations carry a seasonal operating line of credit, drawn down through spring and summer to cover input purchases before harvest income arrives, then paid back down once settlement checks land. Both the draws and the payments appear on the bank statement as large, unremarkable-looking transfers, easy to mistake for ordinary income or expense if they aren't categorized as loan activity specifically.
Keeping loan draws and repayments in their own category, separate from operating income and expense, is what keeps a mid-season draw from inflating an apparent income figure, and a repayment from looking like an unusually large operating cost in the month it happens to clear.
Why the categorized record matters beyond tax season
A clean, categorized transaction history earns its keep well beyond the annual Schedule F conversation. A crop insurance claim can require documentation of actual production and input costs for the year in question. An FSA program enrollment sometimes asks for supporting financial records. A lender renewing an operating loan wants to see more than a single balance — they want a trace of how the money actually moved through a season.
None of these moments announce themselves in advance, which is exactly why building the categorized record as a routine habit — rather than assembling it retroactively under pressure — is worth more than the time it takes in any single season.
CRP and conservation program payments
A Conservation Reserve Program payment, or a payment from a similar conservation program, arrives annually for ground enrolled out of active production — a deposit that looks like ordinary farm income but represents a different kind of revenue entirely, unrelated to any crop grown or sold that year. Read alongside a mix of actively farmed acres and enrolled conservation acres, it's easy for this payment to blend into the general income picture unless it's categorized on its own.
Keeping it separate matters most for an operation evaluating whether a given tract is more valuable enrolled in conservation or returned to production — a comparison that only works if the conservation payment is visible as its own line rather than buried inside a general revenue total.
Who this is for
Row-crop and livestock operators
A season's worth of statements turned into categorized rows without an evening lost to it every time the bank arrives.
Farm families sharing one account
Farm and household transactions separated cleanly instead of untangled by memory months later.
Accountants and bookkeepers serving ag clients
The same categorization method applied regardless of which bank, elevator or co-op a client happens to use.
Operations preparing a loan package
A clean, categorized income and expense history a lender can actually read, built from real statements rather than reconstructed by hand.
This isn't farm management software
Worth being precise about the boundary. This isn't a field-mapping platform, a yield-tracking system, or farm management software that plans planting and tracks input application by acre. There's no integration with equipment telematics or agronomy data. What it reads is the financial side — the bank statement, the settlement statement, the input invoice — the same documents a farm already produces every season, turned into clean, categorized numbers.
Moving from a shoebox or a spreadsheet
Most operations that reach for this have been managing statements the way farms always have — a folder of paper, a shoebox of settlement checks, or a spreadsheet updated in batches whenever tax season or a loan renewal forces the issue. It works, in the sense that the numbers eventually get assembled, but it's slow, and it's the kind of task that gets pushed to January every single year.
The transition doesn't require reorganizing anything on day one. A reasonable first step is running one season's statements through and comparing the categorized export against whatever spreadsheet or shoebox total already exists, to see where the two agree and where the automatic categorization catches something the manual count missed.
How often to run this
Quarterly is a realistic rhythm for most operations — often enough to catch a miscategorized transaction while it's still easy to remember what it actually was, without turning bookkeeping into a weekly chore during planting and harvest when there's genuinely no time for it.
Running it once more right before tax season — covering whatever statements arrived since the last pass — is the point where most operations find the real value: a full year of categorized transactions ready well before the accountant's deadline, instead of a scramble through twelve months of statements in one sitting.
What accuracy actually looks like
A useful way to think about categorization accuracy is the shape of the confidence distribution, not a single percentage. An operation with a small number of clean, recurring suppliers and one primary buyer sees most transactions land at high confidence, with a short list needing review. An operation with many small, irregular vendors and a shared farm-household account sees a longer review list — which reflects how genuinely ambiguous those transactions are, not a weaker tool.
In practice, most row-crop operations with a handful of regular suppliers and one or two buyers see somewhere between 85% and 95% of transactions categorized at high confidence on a first pass, with the rest resolved in a quick review rather than a full manual sort.
Privacy
Uploads go over TLS, encrypted end to end.
Processing runs on EU-hosted infrastructure.
Original documents are deleted immediately after extraction.
Financial data is never used to train AI models.
Full details are on the security page.