For the branch
Record the delivery, sale or deposit in familiar terms. Keep multiple product lines together and attach the deposit slip to the banking record.
← Back to the whole operation
02 / Sales and Branch Activity
A simple entry. A much bigger picture.
Connect what a branch receives, holds, sells and banks. Give the person at the counter a straightforward task, and give management and Accounts the records needed to follow it through.
How this part connects
One sale. A connected branch record.
Receive goods into stock, record sales and send deposit slips to Accounts. Compare stock, sales and deposits for the same branch and period to see what needs checking.
Illustrative process.
For management
Look at sales by branch, product and period. Check that entries have arrived so management can tell a quiet day from a missing submission before acting on a total.
For Accounts
Review transaction records, corrections and exports alongside the ERP. Stock and cash questions can be traced to the entries that created them.
Full process: Sales and Branch Activity
From delivery received to Accounts review
Operation flowRecords to compare
- Delivery receivedMatch dispatch record
- Branch stockReceipts and goods out
- Multi-product saleCustomer, lines, rates
- Deposit and slipBank reference, image
- Accounts reviewReconcile the records
One branch, connected stock and money records
Opening + movementsSales and depositsTransport deliveriesERP, read-only
A delivery adds to the stock record. A sale takes goods out. Accounts compares sales with deposits and their slips for the same branch and period. A sale and a bank deposit are separate entries; they do not always match one for one.
Sales Capture · a closer look
Keep the branch task simple. Keep the record connected.
A branch sale matters to the person recording it, the manager watching activity and the team reconciling the books. The capture design brings those views together.
Illustrative branch activity
What the branch records
- Receive a deliveryRecord the goods and the dispatch reference.
- Record a saleChoose the customer, add product lines, quantities and rates.
- Record a depositAdd the bank reference and a photo of the slip.
A demonstration of the workflow, with no customer records or realised results.
The same entries serve different readers
The branch deals with a sale or a delivery, not a monthly reporting exercise. Management sees the activity and whether entries are missing. Accounts gets records and exports to check against stock movements, transport deliveries and ERP entries.
Dependable mechanics behind the simple task
A stable submission identity distinguishes a retried delivery from a new transaction. Recovery follows that identity, and corrections keep a history. These choices make delayed delivery and amended records easier to investigate.
Branch capture does not depend on the office connection being available. The branch still needs its own connection to submit; this is not offline capture. Delayed transfer to the office is a separate recovery path.
Case study of the capture design and tested workflows. Business acceptance and balance checks govern the full rollout.
Across departments
How this connects to the rest of your business
From truck to branch
Follow the load across the handover between dispatch and the branch.
Explore this partWhat should be in stock
Check opening stock and deliveries against sales, other movements and the stock count.
Explore this partSales and deposits for Accounts
Find missing entries or differences between sales and deposits, then check what explains them.
Explore this partCan your branch team and Accounts follow the same transaction?
Bring a question your team needs to answer. We will walk through the work and the records with you.