---
title: "Andy R (@erpnova) | Hashnode"
description: "Founder at ERPNova.co. Company has expertise in the building the AI implemented ERP Solutions for our Manufacturing customers."
url: "https://hashnode.com/@erpnova"
---

@erpnova

# Andy R

@erpnova · Chennai, India · Joined July 2026

## Comments

[Agreed. I’d recheck permissions and business rules at commit time because things can change while a draft is waiting. If someone posts the invoice manually in the meantime, the middleware should catch that before creating a duplicate. That’s what makes the boundary useful: a model upgrade can change what the agent proposes, while the rules for posting stay the same.](https://hashnode.com/posts/agentic-erp-fails-at-the-integration-layer-not-the-model-layer/6a96902b7bd835b82380c82c/comment/6a9699d2d3445c329464ffb6#reply-6afe2d3e43ed994794f68560)

Reply · Article · 1d ago · [Agentic ERP fails at the integration layer, not the model layer](https://hashnode.com/posts/agentic-erp-fails-at-the-integration-layer-not-the-model-layer/6a96902b7bd835b82380c82c)

[I’d use dedicated test users with the same roles and record permissions as real buyers, approvers, and delegates. That way we test the access each person actually has without using anyone’s login. Amended PO: Check whether a change that requires fresh approval sends it back for sign-off. Split lines: Check that the approval threshold applies to the full PO total. Delegation: Confirm the substitute can approve during cover and loses that ability when it expires. I’d save those as short test scripts so the team can rerun them after an upgrade.](https://hashnode.com/posts/frappe-erpnext-approval-workflows-access-testing/6afd60480215d764c9740aae/comment/6afe0a56490a90911cb71418#reply-6afe15d10371044821c12534)

Reply · Article · 1d ago · [Frappe ERPNext Approval Workflows: Test Access Before Automating](https://hashnode.com/posts/frappe-erpnext-approval-workflows-access-testing/6afd60480215d764c9740aae)

[I think it can work on a busy shift if it’s one tap. The operator should be able to pick ‘Unknown’ when the cause isn’t clear, and the shift lead can follow up at handover. If a bad lot is suspected, capture the lot number at the time of issue so it can be traced later.](https://hashnode.com/posts/frappe-erpnext-manufacturing-planned-actual-material-use/6afd60dab2fcb6d1098ba6f0/comment/6afdd3b77a35787d0bbb411f#reply-6afe15384a40aceeff85ab28)

Reply · Article · 1d ago · [Frappe ERPNext Manufacturing: Compare Planned and Actual Material Use](https://hashnode.com/posts/frappe-erpnext-manufacturing-planned-actual-material-use/6afd60dab2fcb6d1098ba6f0)
