Skip to main content
GullySystem

Recording caked and torn bags as write-offs

Damage, caking and write-offs records hardened or torn bags by grade with a reason. It takes them out of saleable stock and keeps every write-off for the owner to review. A leaking roof or a split stitch leaves a trace in the book. Loss is seen, not absorbed.

What a fertiliser write-off record keeps

One write-off is a short record of what was lost, where and why. The person who found the damage makes it, and the owner reads it later. Four fields carry the story of each bag. They are filled in at the stack.

Grade, bags and batch mark

The entry names the grade, the number of bags and the batch mark printed on the sack. A single hardened bag of ammonium sulphate and a whole bottom row of urea are both written down. Size does not excuse an entry.

Reason for the loss

Each entry carries a reason such as caked by damp, split in stacking or torn at the gate. A reason chosen from a short list can be counted later. A note adds what the list cannot say.

Stack, bay and date

Each entry names the stack and bay the bags came from, and the date. When a pattern appears, the owner sees which stack leaked. A roof repair can then be argued from evidence. Evidence replaces guesses.

Review by the owner

Every write-off waits in a list for the owner. Reading it at month end is the habit. The owner can accept an entry, ask a question or send it back. Nothing vanishes quietly, and nothing is hidden.

Spotting and recording damage through the year

Damage comes in two ways. A sudden loss shows at the gate or in the stack. A slow loss creeps up from the bottom row as the damp season goes on. Four situations show how each reaches the book and the owner.

A hardened bottom row

After a week of rain, the storekeeper lifts the dunnage and finds the lowest row of urea set hard. Bags are counted, the batch mark noted and the loss entered against the stack. They leave saleable stock at once.

A sack split by the loader

During stacking a sack of complex fertiliser tears and spills. The loose fertiliser is entered as bag equivalents, with the reason marked as split in stacking. No bag goes missing. Shed and ledger stay level.

Torn bags found at the gate

A lorry arrives with sacks already torn. They are flagged on the truck receipt, and the same bags then move into the write-off list. Entries keep the link to the receipt for any claim. The link is kept.

The month-end review

At the close of the month, the owner opens the write-off list by grade and by stack. A cluster on one bay prompts a visit. Entries that look odd are queried with the storekeeper before they are accepted.

Who records and who reviews damage

Finding damage and judging it are separate jobs. The record keeps them apart. The storekeeper writes, the owner reads and the accountant takes the figures. Other roles see only the effect on stock. That split is deliberate.

For the storekeeper

Writes down every torn or caked bag with its batch mark and a reason. Every bag is named. A storekeeper who records honestly is protected by the trail, because the owner can see the stack that caused the loss.

For the owner

Reads write-offs by month and by grade and decides which to accept. Sees the stack behind each. Uses the pattern to fix a roof or move a lot. Raises claims with companies from the receipt link.

For the accountant

Reads accepted write-offs and exports them for the books, with grade, bags and reason. The loss is booked from a list that was reviewed. Stock value in the books matches the shed. It does not rest on a wish.

For counter staff

Do not enter write-offs. They see that a written-off bag has left saleable stock, so a farmer is never billed for a hardened bag. The count at the counter is the count that can be sold.

Decisions to settle before write-offs begin

Write-offs lower stock and profit, so the rules around them need to be firm. Four decisions with the owner and the storekeeper settle what counts as a loss and who decides. Each protects the shop and the honest storekeeper. Decide before the first entry.

Who writes off and who approves

Decide that the storekeeper records and the owner approves. A single person doing both removes the check that makes write-offs credible. Write the rule down so it holds in every season, busy or quiet. One rule, written once.

What counts as damaged

Agree where a lumpy bag that can be broken up ends and a write-off begins. Whether partly caked stock is sold at all is the owner’s call, taken with an adviser. The rule is fixed before the first entry.

How damaged stock comes across

Hardened and torn bags found during the opening count are kept apart from saleable stock and entered as write-offs from day one. Your office checks the count. The first book therefore starts clean, with no hidden losses.

Which report matters first for damage caking and write offs

Start with write-offs for caked and torn bags, by grade. Read the last season’s paper notes beside it for one month. If the owner can name the stack for each loss, the record is working. Name the stack.

How write-offs connect to the rest of the product

A write-off sits where stock, the gate and the books meet. It reduces stock, may trace back to a truck and goes to the accountant. Five links keep a damaged bag from staying on the shelf as if it were still saleable. Each one follows.

  • Written-off bags leave saleable stock at the moment of entry
  • Torn sacks flagged at the gate carry across from receipts
  • A low-stock alert fires when a grade runs low
  • Sale register stock columns show bags that left without a sale
  • Accounting export carries accepted write-offs to the books

Where damage write-offs stop

This record shows what was lost and why. It does not prevent damp, repair a roof or decide whether the company or an insurer will bear a loss. Those matters stay with the owner and the company’s representative. A shop with a handful of bags and a dry shelf can note damage in a book.

FAQ

Frequently asked questions

What happens to a bag torn in the shed?

It is written off with its grade, batch mark and reason, and it leaves saleable stock at once. If part of the bag is intact, the owner decides what becomes of it. Either way, the choice is on the record.

How is a write-off different from a stock correction?

A write-off names the grade, reason and stack, and waits for the owner’s review. A correction changes a figure after a count. Keeping them apart stops loss from hiding inside an adjustment. Each has its own list.

Can a write-off be linked to a truck receipt?

Yes, when the damage was found at the gate. Torn sacks flagged on the receipt move into the write-off list with the link kept. Any claim with the company starts from that receipt. The trail is short.

Who sees how much stock was written off?

The owner reads the list by month and grade, and the accountant receives accepted entries for the books. Counter staff see only that the bags are no longer saleable. The storekeeper sees their own entries.

What does the owner look for in the monthly list?

Clusters. A run of losses on one stack, in one grade or from one batch tells more than a single loss does. The list shows each, so the owner can question the roof, the stacking or the supplier. Patterns carry weight.

Where it fits

How this feature fits the system.

Fertiliser Dealer Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.

Truck receipt and bag count

The count at the gate is booked against the company invoice by grade, and shortages or wrong grades are recorded before the driver signs.

Goods Receipt (GRN)

Grade and warehouse stock

Stock is held by grade, bay and stack, so the counter knows which shed to send a loader to for forty bags.

Warehouse Management

Company allotments and indents

Allotments, lifted quantities and pending balances sit beside each indent, so the next order to the company is placed against real figures and not a remembered total.

Purchase Order Management
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements