Delivery Attempt
हा आशय अद्याप मराठीत उपलब्ध नाही.
A delivery attempt records what happened when the agent reached the buyer: what was accepted, what came back, and what was collected.
Overview
Section titled “Overview”Every attempt is recorded, successful or not. That history is what lets you tell a buyer who claims they were never visited exactly when the agent arrived, and it is what identifies addresses that repeatedly fail.
Prerequisites
Section titled “Prerequisites”Before you begin
- The party exists and is active
- The items you need exist with a unit of measure
- The financial period you are posting into is open
Opening the screen
Section titled “Opening the screen”- Delivery
- Transactions
- Delivery Attempt
Procedure
Section titled “Procedure”Open the consignment on the agent app
The agent opens the consignment from their route list. The buyer, address and lines are shown.
Record what the buyer accepted
Enter accepted quantity per line. Where the buyer rejects produce, record the rejected quantity and a reason — quality, shortage or damage.
Capture proof of delivery
Take the buyer signature or the one-time code, plus a photograph where your configuration requires it. Proof of delivery is what settles a later dispute.
Collect payment, if due
For cash-on-delivery, enter the amount collected and the mode. The agent is accountable for it until it is reconciled at the depot.
Submit the attempt
Submit. The order moves to Delivered, Part Delivered or Undelivered depending on what was recorded.
अपेक्षित परिणाम
The order status updates, the returned quantity goes back into stock as a return, and the invoice can be raised for the accepted weight.
Field reference
Section titled “Field reference”| Field | Type | Required | Default | Description | Notes |
|---|---|---|---|---|---|
| Document No. | Auto | Read-only | — | Number allocated from the Delivery Attempt series when the record is saved. | Gaps are not permitted; cancel rather than delete. |
| Date | Date | Yes | Today | Effective date of the transaction. | Must fall inside an open financial period. |
| Party | Dropdown | Yes | — | The account this transaction is raised against. | Only active parties are listed. |
| Reference | Text | No | — | The other party's document number, for reconciliation. | |
| Narration | Text area | No | — | Explanation carried through to the ledger and the printed document. |
Delivery Attempt fields
Important notes
Section titled “Important notes”Common problems
Section titled “Common problems”The Save button is disabled
A required field is empty or invalid. Fields in error are outlined in red with the reason underneath — scroll up, the first error is usually in the header.
You do not have permission to perform this action
Your role is missing the relevant permission for this screen. Ask an administrator to check it against Roles & Permissions.
The period is closed
The date falls in a financial period that has been closed. Either use a date in an open period, or ask an administrator to reopen it — which affects everyone, so it is rarely the right answer.
The rate comes in as zero
No price is configured for that combination of party and item on this date. Check the applicable price list, and whether its validity window covers the document date.
Frequently asked questions
Section titled “Frequently asked questions”Can I edit a delivery Attempt after saving?
While it is still in Draft, yes — every field is editable. After confirmation only non-financial fields such as Narration can be changed; anything else requires cancelling and re-raising the document.
Why is the document number not sequential?
Numbers are allocated when a document is saved, so a cancelled document leaves its number used. That is intentional: a gap-free series is what makes the audit trail defensible.
Can I change the date after confirming?
No. The date determines which period the entry posts into, so changing it would move an already-posted entry between periods. Cancel and re-raise with the correct date.