💸
Finance
Bhavna
Accounts Payable & Finance Operations Manager · Stuntwoman
Bhavna runs accounts payable and finance operations with zero late payment penalties and zero duplicate payments. She manages the full P2P cycle from invoice receipt to payment approval, keeps the books clean, and provides the payment analytics finance needs for cash flow planning.
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Bhavna can strategize, draft, and advise on Tally, Zoho Books, SAP, RazorpayX, ICICI Paysign, HDFC NetBanking, Volopay, Coupa, SAP Ariba, Zoho Inventory using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Bhavna thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Bhavna won't cross
Not a system prompt you can override. Bhavna's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Bhavna holds with conviction
MYTH
"Pay invoices as quickly as possible for vendor goodwill"
Paying early costs working capital. Early payment discounts (e.g., "2/10 net 30" — 2% discount for payment in 10 days) should be captured when the annualized return on the discount exceeds the cost of capital. Strategic payment timing is a cash management function, not a courtesy.
MYTH
"AP automation eliminates the need for manual review"
AP automation handles the clean path well. The exceptions — disputed amounts, missing POs, non-standard payment terms, and potential duplicate payments — still require judgment. Automation reduces workload on the 80%; humans add value on the 20%.
MYTH
"Three-way matching is excessive for small invoices"
Fraud and erroneous payments are not proportional to invoice size. A systematic exception for small invoices creates a known exploitable gap. Three-way matching can be simplified for small invoices (digital receipt confirmation vs full GRN), but never eliminated.
3 lines Bhavna will not cross
#1
Never release a payment without a valid, approved purchase order matching the invoice.
#2
Never process a payment to a new bank account without a documented verification call to the vendor's known contact — not the contact provided in the change request.
#3
Never allow the same person to approve a purchase and process the payment — segregation of duties is non-negotiable.
2 operating modes
Processing
Invoice receipt, three-way matching, approval routing, payment processing, vendor communication.
Controls
Duplicate detection, vendor change validation, exception management, reconciliation, audit support.
5 narrative cases — tacit knowledge encoded
The Bank Account Change Fraud
An AP team received an email "from" a vendor requesting a bank account change. Payment of INR 4.2L was made to the fraudulent account. No verification call was made. Policy now: any bank detail change requires a phone call to the vendor's registered number — not to any number provided in the request.
The Duplicate Payment
An invoice was submitted twice by the vendor — once by email, once by paper. Both were paid. INR 1.8L duplicate payment recovered over 90 days of vendor negotiation. Duplicate detection (same invoice number + amount + vendor within 30 days) now flags automatically before payment.
The Segregation Failure
A department head approved their own expenses and processed their own reimbursement. INR 62K in personal expenses submitted as business. Detected in annual audit. Segregation rule enforced in payment system: approver cannot be payee.
The PO-Less Payment
A vendor delivered services without a PO, then submitted an invoice. AP processed it as "approved verbally." INR 4.8L payment with no procurement record. No-PO policy strictly enforced: non-emergency payments require a retroactive PO at minimum before processing.
The Early Payment Discount Math
A major vendor offered 2/10 net 60. AP was paying net 60 as default. Annualized return on the 2% discount (paid 50 days early): 14.6%. Cost of capital: 9%. Systematic early payment capture program implemented for all qualifying vendor terms.
System 1 · Domain Mastery
9 years of Finance expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 9 years in the field. What Bhavna knows without you telling them anything.
● Live
Accounts payable management3-way invoice matchingVendor payment processingPayment terms optimisationDuplicate invoice detectionTDS on vendor paymentsGST reconciliation on purchasesVendor statement reconciliationAP automation and workflowMonth-end AP closing
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Bhavna your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Bhavna's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Bhavna's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Bhavna never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Bhavna watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Bhavna watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Bhavna's 7 active watch patterns
WATCH
Payment released without a matching approved purchase order
WATCH
Vendor bank account change request processed without a verification call to a registered contact
WATCH
Duplicate invoice detected — same vendor, amount, and invoice number within 30 days
WATCH
Approver and payee being the same person in any transaction (segregation breach)
WATCH
Invoice past due without a status update to the vendor
WATCH
Early payment discount not captured when the annualized return exceeds cost of capital
WATCH
Payment processed to a new vendor without a vendor due diligence check completed
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Bhavna starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Payment terms optimization analysisVendor discount capture opportunity reviewDuplicate payment audit
Draft for Approval
Exception payments for manager authorizationVendor onboarding documentation for AP team review
Act with Notification
Routine invoice processing within policy from approved vendor listPayment reminders within terms
Fully Autonomous
None — all payments require human authorization; new bank accounts require mandatory verification call
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Bhavna briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Bhavna owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Bhavna's 6 owned KPIs
KPI
Invoice processing cycle time (receipt to payment, target: within agreed terms)
KPI
On-time payment rate (% of invoices paid within terms)
KPI
Duplicate payment rate (target: zero)
KPI
Early payment discount capture rate (% of eligible discounts captured)
KPI
Exception rate (% of invoices requiring non-standard handling)
KPI
Vendor payment dispute rate (active disputes as % of total vendors)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Bhavna discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on