Plant Output Should Stay Out of the Bank File

The bank wants proof of output and open orders, so someone copies numbers out of the plant system. Those copies age the moment they leave, and the plant keeps moving. After you read this, you can decide what stays in the production system and what, if anything, belongs in a file for the lender.

Why a copy becomes another plant

A production system is the software that records work orders, finished goods, and supplier receipts as they happen. When you export those figures into a spreadsheet for the bank, you create a second version that no longer updates. The plant still ships and receives, but the file does not, so the office then spends time matching two pictures of the same week.

That extra file often lives on a shared drive or in email, and people treat it as current because it looks finished. It is only a snapshot, a picture of the numbers at one moment. A lender who reads it is reading an older floor, not the one running now.

Manufacturers in Orangeburg meet this request often because inventory and output sit at the center of many loan reviews. The ask is fair, but the risk starts when the answer leaves the system that still changes every shift.

What already lives in the plant system

Finished units and scrap already sit in the production system if the floor is posting them. Work in process, which means jobs started but not finished, sits there as well. Open purchase orders and receipts already sit there if receiving is posting them. Those records are the ones the bank is trying to see, so a copy only repeats them in a new file.

If posting is late or incomplete, a spreadsheet will not fix that gap. It will only hide the gap until the next question from the bank. The first task is to see whether the plant system already holds the fields the lender wants.

You can list which systems hold orders and output without buying anything new. Note the production system, the purchasing system if it is separate, and any spreadsheet that already feeds the bank. Further reading on an applications inventory can help you structure that list, but a notebook and last month's pack are enough to begin.

The plant system is often an ERP, which is the main software for orders, inventory, and production. Purchasing may live in the same place or in a second tool. The bank file is usually neither of those, because it is a file pulled from the system that someone formatted so a lender can read it.

Here is what to gather before you decide whether a copy is even needed.

Production system. Write the name of the software that holds work orders and finished goods.
Supplier orders. Write where open purchase orders and receipts are posted.
Last bank pack. Keep the last file you sent so you can see which fields were copied.
Who exports. Name the person who builds the file and how often they do it.
Who posts. Name who updates the floor and receiving during a normal week.

How the bank file falls behind

The floor does not stop when the export runs, so later postings never reach the file. A pallet can ship after lunch, a receipt can be posted, or a job can be scrapped. By the time the pack reaches the bank, the plant has already moved. If the next question comes later, people open the old file instead of the live system.

Version mix-ups are common because the file is easy to duplicate. Someone saves a copy to email, and someone else saves a copy to a desktop. The production system has one current record, but the copies do not, so no one knows which file was sent.

Watch for these warning signs that the file has become a second plant.

Stale totals. The units in the file do not match what the floor can show today.
Manual edits. Someone typed over an exported number to make a row look right.
Split sources. Output came from the plant system, but orders came from a buyer's inbox.
Old names. The file still uses job names the plant retired last quarter.
Late posting. The export ran before receiving finished the day's receipts.

Checks to run before you send

You can test the next pack against the live system without a special project. Pull the same date range in the production system that the file claims to cover. Compare units, open orders, and receipts for a short sample, because a full plant count is more than you need for this test.

Do this on a normal week, not only when a loan review is due. If the numbers already match, the copy is repeating work that the system already did. If they do not match, the copy is hiding a posting problem that the bank file will not solve.

Run these checks before the next pack goes out.

Match units. Compare finished goods in the file to the same date in the production system.
Match orders. Compare open supplier orders in the file to purchasing in the live system.
Check the clock. Confirm the export time and whether receiving had finished posting.
Find typed cells. Look for numbers that were changed after the export.
Ask the floor. Confirm that a sample job on the file still exists and still has that quantity.

If a line fails a check, do not fix it in the spreadsheet. Open the job or the receipt in the production system, correct the posting there, and run the export again only after that correction is saved.

What to keep inside the system

Factory output should remain in the production system because that is where it is posted and corrected. Supplier orders should remain there, or in the purchasing tool if that is separate, because receipts have to match them. The bank can still receive a report generated from the live system, and that report should stay free of typed totals.

If the lender needs a spreadsheet, generate it from the system and leave the cells unchanged if you can. Do not type over totals to make a covenant, which is a loan rule the bank tracks, look better. If a total is wrong, fix the posting in the plant system and run the report again.

Some teams keep a folder of old packs for history, and that is fine if each file is labeled with the export date and never edited later. Treat those files as letters about the record, because trouble starts when they become the place people look first. The live system remains the record you correct, and the pack only describes it for a date.

Questions the office should ask

The owner, the plant manager, and the person who builds the pack should sit down with last month's file. The goal is to decide what the bank actually needs and whether the production system can produce it. You do not need a new tool to have that talk.

Work through this list and write the answers next to last month's pack.

What fields. List which columns the bank used and which ones were extra.
What date. Note the period the pack covered and whether posting was complete.
What source. State whether every column came from the production system or a side file.
What edits. Record who changed a number after the export and why.
What next. Decide whether the next pack can be a system report with no typed totals.

If the bank needs a covenant test, calculate it from the system report rather than a parallel workbook. If they need a narrative, write it in a cover note and leave the numbers in the report. That split keeps the plant record intact and still answers the lender.

If staff are unsure which system is current, read the FAQ after you finish this review, because it covers common questions about where records should live. Then return to the pack and mark each column with its source. A column without a source is the one most likely to be typed.

Key takeaways

Factory output and supplier orders belong in the production system that posts them.
A bank file is a snapshot, and it ages as soon as the floor moves.
Compare the next pack to the live system before you send it.
Fix posting errors in the plant system before you touch the export file.
Label old packs by date and stop using them as the working record.

Owners can settle this without new software by comparing one pack to the live system. Keep output and orders in that system, and send the bank a report you do not edit by hand. Third Shift Group LLC publishes this for manufacturers in the Orangeburg service area.