Skip to app details
Back to app library
APPNEURAL APP FAMILYFinance

Purchases

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.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
A purchase from request to bill
Request50 branded mugs
Purchase orderAccepted by the vendor
BillMatched and paid
02 / CAPABILITIES

Built around the work you do.

What Purchases does for you.

01

Requests and approval

Anyone on the team asks; approval goes by amount to a buyer or the owner.

02

Purchase orders

GST lines with HSN/SAC, a printable PO and a vendor link to accept or decline.

03

Receiving and bills

Goods received in parts and vendor bills matched to the order, with flags when they differ.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Purchases. What you can do depends on your access in the app.

01

Add vendors

Add vendors with GSTIN and terms, or pick them from Contacts.

02

Order

Turn an approved request into a purchase order and send the vendor its link.

03

Receive and pay

Record what arrived, match the bill and record the payment with its UTR.

YOUR NEXT MOVE

Make Purchases part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Buying for a connected domain: vendors, purchase requests approved by amount, GST purchase orders with a vendor link, receiving and vendor bills matched to orders and receipts.

Employee claims belong to Expenses; recurring subscriptions to tools belong to Renewals; vendor people belong to Contacts.

Priority
P2
Portfolio
Finance
Capability
Finance
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

purchase schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

purchases.appneurox.com DEPLOYED

purchases.appneurox.com

Worker
purchase-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:12
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/purchase-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app