Redefining Technology
  • Case studies
  • Automotive OEM
  • Inward
  • Case study

GRN Automation: From Gate Entry to SAP Posting

GRN automation as our co-founder builds it: the truck's documents photographed at the gate, 27 to 30 checks per document, and a GRN posted to your ERP.

By Atomic Loops · With Vinay Phadnis, Co-founder · Published 11 November 2026

Vinay Phadnis, Co-founder, Atomic Loops
Plant
Automotive OEM, inward gate
Process
Gate entry to GRN in the ERP
Data
Invoice, LR, e-way bill, ASN no., PO
Changed
Clean sets post at the gate; exceptions go to an admin
In this case study

What you are looking at

In this video Vinay Phadnis, co-founder of Atomic Loops, walks the inward gate the way his team automates it: the truck's invoice, lorry receipt, e-way bill and ASN number photographed at the gate, checked against the purchase order and posted as a GRN in the ERP.

He then follows a set with a wrong HSN code or quantity through the admin, the AI co-pilot and the supplier's revised invoice. The worked example below runs both paths at one gate.

  • 27–30 checkpoints per document17
  • GRN posted to SAP, Oracle or Dynamics25
  • Supplier follow-up every few hours34
  • Clean sets post from day one27
Figure 1

The inward gate as one data path

One truck, one phone at the gate: the document set goes up as photos and comes back as a GRN number and a printed sticker. A discrepancy takes the amber branch to the admin.

StopWhoWhat happens
1Document setTruck driverInvoice, lorry receipt (LR), e-way bill, purchase order and the supplier's ASN number
2PhotosGate clerk or securityThe set is photographed on a smartphone or placed on a scanner at the gate
3AI checksAtomic Loops AI layersOCR reads any layout, printed or handwritten; about 27 to 30 checkpoints per document; every line matched to the PO; LLM cross-check
4GRN numberYour ERPAn automated entry creates the GRN for the inward transaction in SAP, Oracle or Microsoft Dynamics
5StickerGate clerkGRN sticker on the phone, copies printed with one button, the screen turns green
6Material movesWarehouseWith its GRN number the material is accepted into the factory
7ExceptionAdmin, AI co-pilotA discrepancy goes to the admin: approve, or the co-pilot emails the supplier and follows up until a revised invoice passes the same checks

Process: as Vinay Phadnis, Co-founder, Atomic Loops, describes it in the recording of 11 Nov 20262617282930323336. Drawing: schematic of an inward gate, not a specific plant; the sticker's fields are not shown.

What it is

GRN automation: a GRN from a photo of the document set

GRN automation is the goods receipt note (GRN) created by software instead of by a clerk: the truck's document set is photographed at the gate, read, checked against the purchase order and posted to the ERP. A clean set gets its GRN number without anyone retyping it; a set with a discrepancy goes to a person.12

In SAP, the GRN is the goods receipt posted against the PO, which the system numbers as a material document. The same flow posts to Oracle or Microsoft Dynamics.34

The worked example

Two trucks at one gate: one GRN in minutes, one held for the supplier

One inward gate at an automotive OEM plant on a weekday first shift, and the two paths our co-founder Vinay Phadnis walks through in the video, a clean document set and a set with a discrepancy.5

Truck A, 08:10. The driver hands over the invoice, lorry receipt, e-way bill and the supplier's ASN number. The security guard photographs them on the gate smartphone and every checkpoint passes against the open PO.67

The GRN number is created in the ERP, the GRN sticker appears on the phone and one button prints copies for the material. The screen turns green, and by 08:16 the load is on its way to the warehouse.67

Truck B, 10:40. Same photos, same checks. Line 3 carries an HSN code that differs from the PO line, and the invoice bills 1,200 pieces against an open PO quantity of 1,000. The set is escalated to the admin, who hands it to the AI co-pilot.89

By 10:48 the supplier has both discrepancies in writing, and the held part is on the planning committee's dashboard with an ETA. The revised, signed invoice arrives at 09:20 next morning, passes the same checks, and Truck B's GRN posts.1011

Figure 2

Two trucks at one gate: one GRN in minutes, one held for the supplier

Truck A's clean set goes from photos to a green screen between 08:10 and 08:16. Truck B's set is escalated, the supplier has both discrepancies in writing by 10:48, and its GRN posts after the revised invoice passes at 09:20 next day.

Times and quantities: illustrative56810. Steps: the clean set and the exception path as recorded7911.

AI impactNobody checked a line by hand on either truck, and Truck B's discrepancy reached the supplier in writing eight minutes after the photos, with an ETA on the dashboard instead of a phone call.10

Why it matters

No GRN, no entry: how one held invoice reaches the production schedule

Vinay's first rule of the inward gate: unless a GRN number is created, the material cannot be accepted into the factory. The same number tracks that raw material or bought-out part from inward through the plant to its finished-good location, so a wrong GRN is a traceability error, not only a receiving error.1213

For inbound logistics at an automotive OEM plant the delay runs in a straight line: a held document set keeps stock out of the warehouse, warehouse stock feeds the production schedule, and a part that is not there becomes unplanned downtime from a stock-out.14

The manual check that guards this gate costs human time on every document, invites human error and leaves room for missed rules and validation checkpoints. Finance carries the result too: under GST the supplier's tax invoice is the plant's document for input tax credit.1516

Figure 3

No GRN, no entry: how one held invoice reaches the production schedule

The delay runs in a straight line from a document discrepancy to a stock-out. Blue marks where the system acts on each link; the tags name what the plant measures.

Chain: as Vinay Phadnis, Co-founder, Atomic Loops, describes it in the recording of 11 Nov 202612131415. Measures: the section's AI impact list.

AI impact
  • Clean sets get their GRN at the gate: measured as time from gate entry to GRN number.
  • Held sets are visible with status and ETA: measured as hours each set waits for its GRN.
  • Fewer stock-out surprises for planning: counted as stoppages traced to material held at the gate.

The checks

The 27 to 30 checkpoints: what is read on each document, and against what

After the photos, the system checks about 27 to 30 checkpoints within each document, against what Vinay calls nationally verified accounting principles: taxation, HSN codes, part numbers, product and pricing totals.1718

Each document has to pass its own rules, and the invoices and purchase orders, lorry receipt, e-way bill and ASN number have to agree with each other before the set counts as a valid gate entry document.18

GST law is what makes that triangulation possible. A tax invoice must carry the HSN code, description, quantity, taxable value, rate and amount of tax. The e-way bill's Part A repeats the invoice number and date, the value and the HSN code, and carries the transport document number, for a road consignment the lorry receipt (LR).1920

Show as a table
Checkpoint groups named in the recording, and what each is compared with
Checkpoint groupRead fromChecked againstA fail looks like
GST rate and tax amountinvoice linesPO line, invoice arithmeticrate on a line differs from the PO
HSN codeinvoice, e-way billPO line, the other documentscode differs from the PO line or between documents
Part numberinvoice, ASNPO linepart not on the PO
Part quantityinvoice, ASNopen PO quantitymore invoiced than is open
Product and pricing totalsinvoicePO price, line and invoice totalstotals do not add up
Document identityinvoice, LR, e-way bill, ASN numbereach otherinvoice or LR number differs across documents
181920
Figure 4

The checkpoints: what is read on each document, and against what

Six checkpoint groups named in the recording, read from four documents and checked against the PO line and each other. GST law makes the cross-check possible: the e-way bill repeats the invoice's number, value and HSN code and carries the LR number.

Groups: as named in the recording; the full list of about 27 to 30 checkpoints per document is not shown1718. Rules: tax invoice particulars, CGST Rules, rule 4619; e-way bill Part A20; HSN digits21; e-way bill number length, GSTN advisory22.

One detail trips simple rule checks: HSN length depends on the supplier, 4 digits on invoices from suppliers with turnover up to Rs 5 crore and 6 digits above, so a short code is not automatically wrong. India note. E-way bill numbers grow from 12 to 14 digits from 1 January 2027, and GSTN has asked ERP providers and integrators to update their validation rules.212223

AI impact27–30 checkpoints per document

Every document set gets the same checks in the same order, whoever is on the gate shift and whatever the supplier's layout.17

Key numbers

27–30
checkpoints verified per document17
3→ 1
departments' manual work before, one flow after38
230set-hours
a day held outside stock at our working-assumption defaults48

Technical implementation

From photo to GRN in SAP: the AI layers that sit on top of your ERP

Automated goods receipt note processing, as we build it, adds AI layers on top of the ERP and MES the plant already runs; nothing in SAP, Oracle or Microsoft Dynamics is replaced. The flow, in the order the system runs it:2425

Figure 5

From photo to GRN in SAP: the AI layers on top of your ERP

The ERP stays the system of record: the AI layers read the purchase order from it and write the GRN back. People appear in two places only: an unclear read, and a discrepancy for the admin.

  1. 1Capture. The gate clerk or security person photographs the invoice, lorry receipt, e-way bill, purchase order and the supplier's ASN number on a smartphone, or places them on a scanner.
  2. 2Read. Our proprietary OCR model digitises each document in any layout, horizontal or vertical, printed or handwritten. A read the model is not confident about goes to a person to confirm.
  3. 3Check. The rule layer runs the checkpoints on each document and across the set.
  4. 4Match. Every line is matched to the purchase order issued to the supplier from the ERP.
  5. 5Cross-verify. A proprietary LLM goes over every stage again, so every supplier's format is reviewed against the same rules and audit guidelines.
  6. 6Post. An automated entry in the ERP creates the GRN number for that inward transaction and returns success, failure or a request for more information.
  7. 7Release at the gate. On success the GRN sticker shows on the phone, copies print with one button and the screen turns green.2627282930

Layers and order: as Vinay Phadnis, Co-founder, Atomic Loops, describes it in the recording of 11 Nov 20262425. Unclear reads to a person, auto-post of clean sets: the deployment decision for this page27. Audit log and guardrails:31. The interface used for the ERP entry is set per plant and is not drawn.

A failure goes down the exception path described next. Every read a person confirmed, every check and every action an agent takes is written to an audit log the plant can review, and agents act only inside the guidelines and guardrails set for them.31

AI impact
  • Gate time per set: photographing and printing, not line-by-line checking.
  • One rule set across every supplier's format, so checks no longer depend on who is on shift.
  • A complete audit trail of what the system read, checked and posted, per GRN.

Exceptions

When the HSN code or quantity is wrong: the admin decides, the co-pilot chases the supplier

A set fails when the GST percentage, the HSN or tax code, the part number or the part quantity does not match what the purchase order expects. The system does not guess: it escalates the set directly to an admin, with the discrepancies listed.32

The admin has two choices. Approve, and the GRN is created automatically and the gate clerk notified. Or hand the case to the AI co-pilot, which emails the supplier the exact discrepancies, explains that the material cannot be accepted without a GRN, and follows up every few hours until a revised invoice arrives.3334

While the case is open, a real-time dashboard shows the planning committee and the plant manager where the material is, its current status and its ETA into the warehouse, so planning can adjust before a stock-out rather than after one.35

When the supplier sends the revised, signed invoice, the same system reads it and cross-checks it with the PO. If everything is correct, the GRN entry posts automatically and the gate guard is notified.36

Figure 6

When the HSN code or quantity is wrong: one decision, then a loop with the supplier

The admin decides once: approve and the GRN is created, or hand the case to the co-pilot. The co-pilot keeps the supplier on a written loop until the revised invoice passes the same checks, while planning sees the ETA.

Path: as Vinay Phadnis, Co-founder, Atomic Loops, describes it in the recording of 11 Nov 2026323334353637.

AI impactEvery discrepancy now gets one decision, one written trail to the supplier and an ETA planning can see, and the admin's decision and each email stay in the audit log.37

Before and after

Three departments before, one flow after

Before, Vinay says, multiple departments checked this process: the gate department verified invoices, procurement talked to suppliers so production was not disturbed, and a supervisor team reported likely stock-outs and time to warehouse to the plant manager.38

Show as a table
Who does what, before and after GRN automation
RoleBeforeAfter
Gate clerk, securityChecks every line of every document against the POPhotographs the set, prints the GRN sticker
AdminNo separate stepDecides each discrepancy: approve, or hand it to the co-pilot
Procurement, buyersPhone and email suppliers for corrected documentsCo-pilot emails the supplier and follows up
Supervisor teamReport stock-out risk and time to warehouseDashboard shows status and ETA of held material
Planning committee, plant managerWait for the supervisors' reportSee every held material live, with its ETA
3839
Figure 7

Three departments before, one flow after

Before, the gate checked, procurement chased and the supervisors reported, each by hand. After, one flow carries the set, the admin is the one decision point, and the dashboard replaces the report.

RoleBeforeAfter
Gate clerk, securityChecks every line of every document against the POPhotographs the set, prints the GRN sticker
AdminNo separate stepDecides each discrepancy: approve, or hand it to the co-pilot
Procurement, buyersPhone and email suppliers for corrected documentsCo-pilot emails the supplier and follows up
Supervisor teamReport stock-out risk and time to warehouseDashboard shows status and ETA of held material
Planning committee, plant managerWait for the supervisors' reportSee every held material live, with its ETA

Before and after: as Vinay Phadnis, Co-founder, Atomic Loops, describes it in the recording of 11 Nov 20263839.

AI impact3 departments → 1 flow

Three departments' manual checks, calls and reports become one automated flow with one decision point, the admin.3839

What it is worth

What held document sets cost your plant a day: a calculator from five numbers

The defaults below are Atomic Loops' working assumptions from our experience of gate and inward operations at automotive OEM plants, and the value case for GRN automation on this page is built on them. Replace each with your plant's number; the range is the spread we plan for.40

  • Document sets a day (inbound trucks): 120 (60 to 200), from the gate register.
  • Manual check per set: 15 minutes (10 to 25) for invoice, LR, e-way bill and ASN against the PO.
  • Sets with a discrepancy: 8% (4% to 15%).
  • Hours to a corrected invoice: 24 (4 to 72), Vinay's "a few hours or a few days".
  • Chasing and reporting per held set: 60 minutes (30 to 120), procurement calls plus supervisor updates.
4142434445
  • Gate checking hours a day = sets × minutes ÷ 60: about 30 (10 to 83).
  • Sets held a day = sets × discrepancy share: about 10 (2 to 30).
  • Held set-hours a day = held sets × hours to a corrected invoice: about 230 (10 to 2,160), each an hour a load waits outside warehouse stock.
  • Chasing hours a day = held sets × minutes ÷ 60: about 10 (1 to 60).
46474849
Figure 8

What held document sets cost your plant a day

Move the five inputs to your plant's values. Each tile shows its formula and where your result sits between the all-low and all-high inputs.

Five inputs: replace each with your plant's number

Gate checking by hand

30hours a day

all-low to all-high inputs: 10 to 8346

sets × minutes ÷ 60

Sets held for a discrepancy

9.6sets a day

all-low to all-high inputs: 2.4 to 30.047

sets × discrepancy share

Loads waiting outside warehouse stock

230set-hours a day

all-low to all-high inputs: 10 to 2,16048

held sets × hours to a corrected invoice

Chasing and status reporting

9.6hours a day

all-low to all-high inputs: 1.2 to 60.049

held sets × minutes ÷ 60

Held set-hours a day against hours to a corrected invoice, at your sets a day

Defaults: Atomic Loops working assumptions from gate and inward operations at automotive OEM plants404142434445. Formulas: the section's own46474849. Hours to a corrected invoice spans the expert's 'a few hours or a few days'.

Figure 9

From five of your numbers to the KPIs the plant manager watches

Your inputs set today's daily cost; the automated check, the early supplier email and the co-pilot's chasing act on three of those figures, which roll up to stock, stoppages and clean books.

Low and high combine all-low or all-high inputs. First order: the check moves to the system, so clerk time per set falls to the photos and the sticker, and the supplier email leaves at escalation instead of when someone finds time.46

Second order: held set-hours shrink as supplier corrections start earlier, chasing hours fall and supervisors stop compiling status reports. At the top: warehouse stock that arrives when planning expects it, fewer stoppages from stock-outs and fewer GST and HSN errors carried into the books.

Values: estimates from our working assumptions46474849. Roll-up: the section's first- and second-order effects; each is measured from your own gate, ERP and dashboard records.

AI impact
  • Gate checking hours: clerk minutes per document set, before and after.
  • Held set-hours: escalation to GRN for every held set, from the dashboard.
  • Stock-outs: stoppages per month traced to material held at the gate.

Our approach

How we start: ROI first, on top of the ERP you already run

We are an ROI-first company, not a tech-first one: the work starts from what held sets and manual checks cost your plant, and the AI is layered onto your existing ERP and MES rather than replacing them. Vinay's team has done GRN implementations across multiple factories, countries and document formats.5051

Figure 10

How we start: numbers first, then live on top of your ERP

Three set-up steps, then go-live with clean sets posting from day one, and a review of the audit log and the dashboard with planning.

  1. 1Put your numbers into the calculator above and agree the baseline with the plant manager.
  2. 2Map your document set and your suppliers' formats onto the checkpoints.
  3. 3Connect your ERP (SAP, Oracle or Microsoft Dynamics) and name the admin who decides discrepancies.
  4. 4Go live: clean sets post from day one, unclear reads go to a person, discrepancies go to the admin and the co-pilot.
  5. 5Review the audit log and the held-material dashboard with planning.52

Steps: Atomic Loops' start sequence50. Phases, not durations.

AI impactFrom the first day, every clean document set gets its GRN at the gate and every exception has an owner, a written trail and an ETA.52

Questions inward and procurement teams ask

Frequently asked questions

Which ERP systems can the GRN be posted to?

The GRN is created by an automated entry in the ERP the plant already runs: SAP, Oracle, Microsoft Dynamics and other ERP systems. The AI layers sit on top of the ERP and MES rather than replacing them, so the purchase order stays in the ERP and the GRN number is created there for each inward transaction.

Does every GRN need a person to approve it?

No. A document set that passes every checkpoint and matches the purchase order gets its GRN automatically, from the first day. A person steps in twice: when the OCR is not confident about a read, someone confirms it, and when there is a discrepancy, the admin approves the GRN or hands the case to the AI co-pilot.

What if a supplier's invoice is handwritten or in its own format?

The OCR model reads each document in any layout, horizontal or vertical, printed or handwritten, in the supplier's own format. A language model then cross-verifies every stage, so documents from every supplier are reviewed against the same rules and audit guidelines. Reads the model is unsure about go to a person to confirm.

What does the AI co-pilot send to the supplier, and how often?

When the admin hands a discrepancy to the co-pilot, it emails the supplier the exact discrepancies, such as a wrong HSN code or a quantity above the open purchase order, and explains that the material cannot be accepted without a GRN. It follows up every few hours until a revised, signed invoice arrives.

Is it possible to completely avoid invoice mismatches through automation?

No. A supplier can still send an invoice with the wrong GST rate, HSN code or quantity. What changes is when and how it is handled: the mismatch is caught at the gate from the photos, the admin decides in one step, and the co-pilot chases the correction while planning sees the held material's ETA.

Sources

  1. Working definition used on this page: GRN automation creates the goods receipt note from the photographed document set (read, checked against the PO, posted to the ERP); clean sets post without retyping, discrepancies go to a person. — Atomic Loops working definition from the recording [03:06-06:47] and the user's deployment decision (ask-20261111-144055-3) 2026-11-11 ↩
  2. A clean document set creates the GRN automatically; a discrepancy is escalated to an admin. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [05:27; 06:41] 2026-11-11 ↩
  3. In SAP a goods receipt is entered against the purchase order (MIGO, Goods Receipt > For Purchase Order); on posting, the system assigns a material document number. — https://help.sap.com/saphelp_46c/helpdata/EN/fd/45bbbd9d6411d189b60000e829fbbd/content.htm undated (SAP Library, release 4.6C) ↩
  4. The GRN can be created in SAP, Oracle or Microsoft Dynamics and other ERP systems. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [02:36] 2026-11-11 ↩
  5. The two-truck case is built on the two scenarios in the recording; all times and quantities in it are illustrative. — Atomic Loops worked example built on the two scenarios in the recording [05:05-08:44] 2026-11-11 ↩
  6. Truck A arrives at 08:10 and its material leaves the gate for the warehouse at 08:16 (illustrative times). — Atomic Loops worked example built on the two scenarios in the recording [05:05-08:44] 2026-11-11 ↩
  7. Clean set: photos taken by a clerk or security person; if all rules pass, the GRN is created, the sticker shows on the smartphone, copies print with one button and the screen turns green. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [05:09-05:48] 2026-11-11 ↩
  8. Truck B arrives at 10:40; invoice line 3 has an HSN code different from the PO line; invoice quantity 1,200 against an open PO quantity of 1,000 (illustrative). — Atomic Loops worked example built on the two scenarios in the recording [05:05-08:44] 2026-11-11 ↩
  9. A discrepancy in quantity and in the HSN or tax code is verified against the PO and escalated to an admin, who can hand it to an AI co-pilot. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [06:19-06:55] 2026-11-11 ↩
  10. Co-pilot email sent at 10:48 (eight minutes after the 10:40 arrival); revised signed invoice arrives at 09:20 the next morning (illustrative; within the expert's 'a few hours or a few days'). — Atomic Loops worked example built on the two scenarios in the recording [05:05-08:44] 2026-11-11 ↩
  11. The co-pilot follows up every few hours; a real-time dashboard shows planning and the plant manager status and ETA; the revised signed invoice is re-read, re-checked against the PO, the GRN posts and the gate guard is notified. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [07:48-08:44] 2026-11-11 ↩
  12. Unless a GRN number is created, the material cannot be accepted into the factory. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [07:13] 2026-11-11 ↩
  13. The GRN number tracks the raw material from inward throughout the factory to a finished-good location. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [01:45] 2026-11-11 ↩
  14. Delay in the GRN hurts warehouse stock, then production schedules; visibility helps reduce unplanned downtime from stock-outs. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [07:24; 08:12] 2026-11-11 ↩
  15. Manual review is labour-intensive, open to human error and to missed rules and validation checkpoints. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [02:49-03:06] 2026-11-11 ↩
  16. Under GST a tax invoice is an essential document for the recipient to avail input tax credit; a registered person cannot avail ITC unless in possession of a tax invoice or debit note. — https://www.gstcouncil.gov.in/sites/default/files/e-version-gst-flyers/Tax_Invoice_and_other_new.pdf undated (CBIC Directorate General of Taxpayer Services flyer; opened 2026-11-11) ↩
  17. The system verifies about 27 to 30 checkpoints within each document. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [09:45] 2026-11-11 ↩
  18. Extracted fields are reviewed against nationally verified accounting principles on taxation, HSN codes, part numbers, product and pricing totals, forming a triangulation of rules each document must follow to be a valid gate entry document; GST %, part number and quantity are checked against the PO. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [03:48-04:09; 05:52; 06:35] 2026-11-11 ↩
  19. A GST tax invoice must contain, among other particulars, the HSN code of goods, description, quantity and unit, total value, taxable value, rate of tax and amount of tax (CGST Rules, rule 46). — https://www.gstcouncil.gov.in/sites/default/files/e-version-gst-flyers/Tax_Invoice_and_other_new.pdf undated (CBIC flyer; opened 2026-11-11) ↩
  20. Part A of the e-way bill comprises GSTIN of recipient, place of delivery, invoice or challan number and date, value of goods, HSN code and transport document number (Goods Receipt Number, Railway Receipt Number, Airway Bill or Bill of Lading Number); required for consignment value above Rs 50,000. — https://gstcouncil.gov.in/sites/default/files/e-version-gst-flyers/51_GST_Flyer_Chapter18.pdf 2018-02-15 (PDF creation date; GST Flyers chapter 18) ↩
  21. From 1 April 2021 a tax invoice must show 4 HSN digits where the supplier's aggregate turnover in the preceding financial year is up to Rs 5 crore and 6 digits above Rs 5 crore. — https://www.gstcouncil.gov.in/sites/default/files/2024-05/notfctn-78-central-tax-english-2020.pdf 2020-10-15 ↩
  22. GSTN advisory: e-way bill numbers change from 12 to 14 digits (consolidated EWB 10 to 11) with effect from 1 January 2027. — https://www.caalley.com/gst26/gst_advisory1104.pdf 2026-11-04 ↩
  23. The advisory asks taxpayers, GSPs, ERP/software providers and API integrators to modify applications, APIs, database schemas and validation rules before 1 January 2027. — https://www.caalley.com/gst26/gst_advisory1104.pdf 2026-11-04 ↩
  24. AI layers sit on top of traditional ERP or MES systems to extract maximum value from them. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [09:15-09:23] 2026-11-11 ↩
  25. The GRN is created in SAP, Oracle or Microsoft Dynamics and other ERP systems. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [02:36] 2026-11-11 ↩
  26. Documents are placed on a scanner or photographed with a smartphone (invoice, lorry receipt, purchase order, supplier ASN number); a proprietary OCR model digitises any layout, printed or handwritten. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [03:14-03:42; 04:29] 2026-11-11 ↩
  27. OCR reads with low confidence go to a person to confirm; clean document sets post the GRN automatically from day one. — Atomic Loops deployment rule, confirmed by the user in the control tower (ask-20261111-144055-3, 2026-11-11) 2026-11-11 ↩
  28. Rule validation and matching against the PO issued to the supplier; a proprietary LLM cross-verifies every stage so all documents follow the same rules, regulations and audit guidelines. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [03:48-04:45; 06:35] 2026-11-11 ↩
  29. An automated ERP entry creates the GRN number for the inward transaction and notifies success, failure or additional information needed. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [04:45-05:05] 2026-11-11 ↩
  30. GRN sticker displayed on the smartphone, multiple copies printed with one button, screen turns green. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [05:27-05:48] 2026-11-11 ↩
  31. Complete observability and audit logs for all AI systems; AI agents operate under strict guidelines and guardrails. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [11:14-11:38] 2026-11-11 ↩
  32. A mismatch in GST percentage, tax percentage, HSN or taxation code, part number or part quantity, verified against the PO, is escalated directly to an admin for approval. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [05:52-06:41] 2026-11-11 ↩
  33. If the admin approves, the GRN is created automatically and the gate clerk notified; or the admin tells an AI co-pilot to take over, which emails the supplier the exact discrepancies. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [06:47-07:07] 2026-11-11 ↩
  34. The email urges a fast reply because without a GRN the material cannot be accepted; the co-pilot follows up every few hours until a revised invoice copy is sent. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [07:13; 07:34-07:48] 2026-11-11 ↩
  35. A real-time dashboard shows the planning committee or plant manager where the material is, its status and its ETA to the warehouse, helping planning reduce unplanned downtime from stock-outs. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [07:48-08:20] 2026-11-11 ↩
  36. The supplier's new signed invoice is read by the same system, cross-checked with the PO; if correct, a GRN entry is automatically posted and the gate guard notified. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [08:20-08:44] 2026-11-11 ↩
  37. Procurement's supplier follow-up and the supervisor team's stock-out reporting are now automated; audit logs cover all AI systems. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [08:52-09:09; 11:14] 2026-11-11 ↩
  38. Before: the gate department verified invoices, the procurement team talked to suppliers, a supervisor team reported potential stock-out and expected time to warehouse to the plant manager; all of this is now automated. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [08:44-09:09] 2026-11-11 ↩
  39. After: photos and sticker at the gate, admin decides discrepancies, AI co-pilot emails and follows up with the supplier, real-time dashboard for planning and the plant manager. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [05:09-08:20] 2026-11-11 ↩
  40. The calculator defaults are Atomic Loops' working assumptions from our experience of gate and inward operations at automotive OEM plants; the page's value case is built on them and the reader replaces them with plant data. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  41. Document sets (inbound trucks) per day: default 120, range 60 to 200. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  42. Manual check time per document set at the gate: default 15 minutes, range 10 to 25. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  43. Share of document sets with a discrepancy: default 8%, range 4% to 15%. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  44. Hours from escalation to a corrected invoice: default 24, range 4 to 72; consistent with the expert's 'a few hours or a few days' [07:45]. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  45. Procurement chasing plus supervisor reporting per held set: default 60 minutes, range 30 to 120. — Atomic Loops working assumption from our experience of gate and inward operations at automotive OEM plants; replace with plant data 2026-11-11 ↩
  46. Gate checking hours per day = sets x minutes / 60: 30 at the defaults, range 10 (60 x 10) to 83.3 (200 x 25). — Atomic Loops estimate from the working assumptions above (calculation in R&D.txt, value_frame 2026-11-11) 2026-11-11 ↩
  47. Sets held per day = sets x discrepancy share: 9.6 at the defaults, range 2.4 (60 x 4%) to 30 (200 x 15%). — Atomic Loops estimate from the working assumptions above (calculation in R&D.txt, value_frame 2026-11-11) 2026-11-11 ↩
  48. Held set-hours per day = held sets x hours to a corrected invoice: 230.4 at the defaults, range 9.6 (2.4 x 4) to 2,160 (30 x 72). — Atomic Loops estimate from the working assumptions above (calculation in R&D.txt, value_frame 2026-11-11) 2026-11-11 ↩
  49. Chasing hours per day = held sets x minutes / 60: 9.6 at the defaults, range 1.2 (2.4 x 30) to 60 (30 x 120). — Atomic Loops estimate from the working assumptions above (calculation in R&D.txt, value_frame 2026-11-11) 2026-11-11 ↩
  50. Atomic Loops is ROI- or solutions-first rather than tech-first, extracting value from existing ERP and MES systems by layering AI on top. — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [10:32-10:47] 2026-11-11 ↩
  51. Atomic Loops has done GRN implementations across multiple factories, countries and document formats (no count or client given). — Vinay Phadnis, Co-founder, Atomic Loops, recorded 2026-11-11 [10:54-11:09] 2026-11-11 ↩
  52. Start sequence (numbers first, map documents and formats, connect the ERP and name the admin, go live with auto-post of clean sets and person confirmation of unclear reads, review audit log and dashboard) is the Atomic Loops way of working; the recording does not describe rollout steps. — Atomic Loops way of working, from the recording [10:32-11:38] and the user's deployment decision (ask-20261111-144055-3, 2026-11-11) 2026-11-11 ↩