Requests and approval
Anyone on the team asks; approval goes by amount to a buyer or the owner.
From request to paid bill, with nothing slipping through
Raise purchase requests, send GST purchase orders to vendors, receive the goods and match the bills.
Each domain keeps vendors with GSTIN (checked, giving PAN and state), address, contact, payment terms and category, optionally picked from Contacts; bank and UPI details are sealed with VAULT_KEY and shown only to buyers who need to pay, with every look audited. Anyone on the team raises a purchase request (PR/<financial year>/0001): it is approved at once up to the auto-approve amount, by a buyer up to the owner's limit and by the owner above it, never by the person who asked. Purchase orders (PO/<financial year>/0001) carry lines with HSN/SAC, quantity, unit, rate and GST, CGST+SGST or IGST by place of supply, the amount in words and terms, and print on A4. The vendor opens /po/<token> in the domain's brand and accepts with a name and an expected delivery date, or declines with a reason, kept as an electronic acceptance record. Goods receipts (GRN) record quantities in parts or a completed service. Vendor bills with their file in R2 are matched to the PO and the receipts, with flags for no PO, more than ordered or received, the wrong tax type, duplicate bill numbers and totals that do not add up; payments are recorded with mode and UTR. Reports of spend by vendor, category and month, open POs, late deliveries and bills due, a CSV purchase register, a daily 10:00 IST digest, an API (orders, bills, requests), webhooks, and Claude to draft a PO from a plain request and compare pasted vendor quotes.
What Purchases does for you.
Anyone on the team asks; approval goes by amount to a buyer or the owner.
GST lines with HSN/SAC, a printable PO and a vendor link to accept or decline.
Goods received in parts and vendor bills matched to the order, with flags when they differ.
A suggested path for Purchases. What you can do depends on your access in the app.
Add vendors with GSTIN and terms, or pick them from Contacts.
Turn an approved request into a purchase order and send the vendor its link.
Record what arrived, match the bill and record the payment with its UTR.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps vendors with GSTIN (checked, giving PAN and state), address, contact, payment terms and category, optionally picked from Contacts; bank and UPI details are sealed with VAULT_KEY and shown only to buyers who need to pay, with every look audited. Anyone on the team raises a purchase request (PR/<financial year>/0001): it is approved at once up to the auto-approve amount, by a buyer up to the owner's limit and by the owner above it, never by the person who asked. Purchase orders (PO/<financial year>/0001) carry lines with HSN/SAC, quantity, unit, rate and GST, CGST+SGST or IGST by place of supply, the amount in words and terms, and print on A4. The vendor opens /po/<token> in the domain's brand and accepts with a name and an expected delivery date, or declines with a reason, kept as an electronic acceptance record. Goods receipts (GRN) record quantities in parts or a completed service. Vendor bills with their file in R2 are matched to the PO and the receipts, with flags for no PO, more than ordered or received, the wrong tax type, duplicate bill numbers and totals that do not add up; payments are recorded with mode and UTR. Reports of spend by vendor, category and month, open POs, late deliveries and bills due, a CSV purchase register, a daily 10:00 IST digest, an API (orders, bills, requests), webhooks, and Claude to draft a PO from a plain request and compare pasted vendor quotes.
Employee claims belong to Expenses; recurring subscriptions to tools belong to Renewals; vendor people belong to Contacts.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
purchases.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.