I want to start with a truthful confession: most businesses I speak with dramatically underestimate how much of what they do every day is pure information shuttling.

By "information shuttling," I mean the activity of taking a piece of information that already exists somewhere in your business — in a spreadsheet, an email, a system — and manually copying it to another place where it's needed. Typing invoice details from a delivery note into an accounting system. Re-entering a confirmed sale from the CRM into the inventory tracker. Forwarding an email approval chain to trigger the next step in a process.

This activity is almost never how it appears on a job description. People are hired as "accounts payable specialists" or "operations coordinators" or "inventory analysts." But when you actually shadow those employees for a day and observe what they're doing hour by hour, a substantial portion of their time — often 40–60% — is information shuttling.

And here's the frustrating thing about information shuttling: it adds no value to the information. You're not making the invoice better by retyping it. You're not improving the customer record by copy-pasting it. You're just spending payroll budget to physically relocate data that shouldn't require human involvement to move. Worse, every manual data movement is an opportunity for human error to introduce inaccuracies that take far longer to detect and correct than the original entry took.

Peppermint exists, fundamentally, to eliminate information shuttling. Every automation capability in the platform is ultimately solving the same problem: making information available where it's needed, when it's needed, without requiring a person to physically move it.

Let's go through the major automation domains in detail.

The Procure-to-Pay Cycle: Seven Days Compressed to Minutes

The procure-to-pay cycle — the sequence of events from identifying a purchasing need to paying a vendor invoice — is one of the longest, most people-intensive, most error-prone processes in most organizations. A typical P2P cycle in a manual or semi-manual environment looks something like this:

Day 1: An operations manager identifies a supply need and sends an email to their manager requesting approval.

Day 1–2: The approving manager responds (or doesn't, because the email gets buried).

Day 2–3: Once approved, the manager emails purchasing, who manually creates a purchase order in the AP system, generates a PDF, and emails it to the vendor.

Day 5–15: The vendor ships the goods. The warehouse receives them, manually notes the receipt on a paper form, and eventually sends it to finance.

Day 12–20: Finance receives a vendor invoice, manually matches it against the PO and the receiving document, and schedules payment according to payment terms.

Day 30+: Payment is released.

At every step, there's a wait. At every step, there's potential for information to go missing, fields to be mismatched, or a person to be unavailable. The friction compounds.

The Peppermint P2P Flow

In Peppermint's automated P2P environment:

Requesting: An operational user logs a purchase request in the system directly, selecting the vendor, item, quantity, and cost center code. The system immediately checks the request against departmental budget — if the request exceeds budget, a flag is raised before the request is submitted, not after.

Approving: The system identifies the correct approver based on the amount and department. A push notification (mobile or email) is dispatched with all relevant details visible in a single view. One tap approves it.

The PO: Approved requests automatically generate a formatted purchase order, which is transmitted directly to the vendor via the vendor portal or email. The PO is logged in both the AP system and the commitment accounting immediately, so it's visible in budget reporting the moment it's created.

Receiving: When goods arrive at the warehouse, the receiving team simply scans the items against the pending PO using a handheld device. The system automatically creates a goods receipt note, updates inventory, and triggers the "ready for invoice matching" status in AP.

Matching: When the vendor invoice arrives, the system automatically attempts a three-way match against the PO and the goods receipt. If quantities and prices match within defined tolerances, the invoice is cleared for payment without human review. Only exceptions — mismatches — surface for human investigation.

Payment: Cleared invoices are automatically grouped into payment runs by due date and vendor, released for authorization with a single approval action.

What took 30 days and multiple handoffs now takes hours at most for routine transactions. Human involvement is concentrated where it genuinely adds value: reviewing exceptions, building vendor relationships, and analyzing spend patterns.

Bank Feed Reconciliation: From a Week to an Hour

Bank reconciliation is one of the finance team's most consistently unpleasant recurring tasks. Downloading bank statements, comparing them line by line against the accounting ledger, investigating unmatch items, making adjusting entries — for a mid-sized company with moderate transaction volume, this can represent 1–2 days of work per month.

Peppermint's Matching Engine

Peppermint connects directly to your banking institutions via secure open banking APIs or direct bank feeds, importing transaction data throughout the day rather than in end-of-day batch files. This real-time import is the first piece.

The second piece is the matching engine. Rather than simple amount-based matching, Peppermint's engine evaluates:

• Reference codes: Does the transaction description contain a supplier reference or invoice number that appears in your AP records?
• Vendor name patterns: Has this payee appeared before and been manually matched to a specific vendor? If so, apply the same match.
• Amount and date tolerance: Within what tolerance band should matches be considered? (Configurable for each account.)
• Transaction category patterns: Based on historical categorization of similar transactions, what account code and cost center should this be posted to?

After initial configuration and a few weeks of learning your transaction patterns, the matching engine typically achieves 95%+ auto-match rates on routine transactions. Your reconciliation work shifts from processing 500 transactions to reviewing the 25 that were genuinely ambiguous.

Over a year, this returns weeks of capacity to a finance team that previously considered reconciliation an unchangeable fact of life.

Revenue Recognition: Eliminating the End-of-Quarter Scramble

Revenue recognition is a perennial headache for businesses that provide services, subscriptions, or multi-year contracts. GAAP requires that revenue be recognized when performance obligations are satisfied — not necessarily when cash arrives or when the invoice is sent. In manual environments, tracking deferred revenue schedules, multi-element arrangement allocations, and milestone-based recognition is a spreadsheet-heavy, error-prone exercise repeated every month.

Peppermint's Recognition Engine

When a contract or subscription is created in Peppermint, the recognition schedule is defined at that moment:

• What is the total contract value?
• What are the performance obligations?
• Over what period is each obligation satisfied?
• Are there variable elements requiring estimation?

The system then automatically generates the revenue recognition entries on the defined schedule — recognizing a portion each month, handling adjustments when contract terms change, and maintaining the deferred revenue liability account accurately without manual journal entries.

When your external auditors request support for your recognized revenue figures, the system can produce a complete recognition schedule for every contract — showing the opening deferred balance, the period recognition, and the closing balance — for any period. No spreadsheets. No reconstruction. The documentation was built as part of the normal operating process.

Inventory Replenishment: From Reactive to Predictive

The traditional inventory management model is fundamentally reactive: you run out of something, then you order more. The operational costs of this model are significant — stockouts that lead to lost sales, emergency freight charges to rush-ship replenishment orders, and customer satisfaction damage that's often invisible in the immediate financial numbers but very real in renewal rates and repeat purchase behavior.

The Peppermint Replenishment Model

Peppermint's inventory module operates on predictive triggers rather than reactive ones.

Demand forecasting: The system analyzes historical sales velocity by SKU, applying seasonal adjustment factors and trend analysis to project forward demand over your supplier lead time window.

Safety stock calculation: Rather than a static, manually-set minimum stock level, the safety stock calculation is dynamic — it considers lead time variability, demand variability, and target service level to compute a statistically appropriate buffer.

Reorder point automation: When projected inventory on hand (current stock minus projected demand over the lead time) approaches the safety stock threshold, the system generates a purchase recommendation. The purchasing team reviews a prioritized list of recommended orders each morning rather than monitoring hundreds of individual SKU levels manually.

Supplier routing automation: For approved vendor relationships with configured ordering minimums, terms, and item-supplier mappings, approved purchase recommendations can automatically generate and transmit purchase orders without additional manual steps.

This shifts purchasing from a reactive firefighting activity to a proactive, analytically-driven function.

Expense Management: The Receipt-to-Reimbursement Refresh

Employee expense management is a small-dollar, high-friction process in most organizations. Employees submit paper receipts or PDFs, managers approve via email, finance data-enters the details, approvals are sought again, and a reimbursement check is eventually issued.

The entire process is inconvenient for employees, difficult to enforce policy against, and time-consuming for the finance team proportional to the dollars actually involved.

Peppermint's Expense Workflow

Employees photograph receipts at point of purchase with the mobile app. OCR technology extracts the merchant, date, and amount automatically and pre-populates the expense entry. The submitter adds the cost center code and expense category, and submits.

The system routes the submission to the appropriate approver automatically — based on the amount, the cost center, and the expense type. Approvers receive mobile push notifications and can approve or query with a single tap.

Approved expenses are automatically integrated into the payroll batch for reimbursement in the next pay run, or into the AP ledger for direct bank transfer, depending on configuration.

Finance's role in this workflow is now exception management and policy compliance review — not data entry.

Reporting and Analytics: From Request Queue to Self-Service

In most organizations, business reporting follows a frustrating sequence: a manager identifies a question they need answered, submits a request to finance or IT, waits for the report to be built, receives a static spreadsheet, and by the time it arrives, either the decision has already been made or the data is stale.

This process exists because financial data in most organizations is locked inside systems that require technical knowledge to query. Business users can't build their own reports, so they depend on technical intermediaries.

Peppermint's Self-Service Layer

Peppermint's reporting layer is designed around the principle that business users should be able to answer their own questions. The interface allows drag-and-drop report building from any data element in the system: select dimensions (product, customer, region, salesperson), select measures (revenue, margin, units), apply filters, and run.

Reports can be saved and shared across teams. Dashboards can be configured by role — the warehouse manager's home screen shows inventory velocity and open purchase orders; the CFO's home screen shows cash position, AR aging, and revenue performance against plan.

Real-time data means reports reflect current actuals, not last night's data extract. A sales director checking performance at 3 PM sees results that include the 2 PM deals.

This doesn't eliminate the need for sophisticated financial analysis — it liberates your analysts from report production so they can focus on interpretation and strategic insight.

Frequently Asked Questions

Q: How long does configuring Peppermint's automation features typically take?

A: Core automation — bank feed matching, AP workflow, basic inventory reorder triggers — is typically configured and operational within the first 4–6 weeks of implementation. More sophisticated features like multi-stage revenue recognition schedules and complex approval hierarchies are configured progressively over the first 3 months.

Q: What happens when automation makes an incorrect match or posts to the wrong account?

A: Errors are surfaced through the exception management workflow rather than silently propagating. Finance administrators can review and correct matched transactions before they're posted to the permanent ledger. The correction also feeds back into the matching engine's learning model, improving future accuracy.

Q: Can we configure approval thresholds differently for different departments or entity types?

A: Yes. Peppermint's approval workflow engine supports fully configurable routing logic. Purchase requests under $500 from the marketing department might auto-approve; the same amount from an entity with stricter controls routes to a manager. These rules are configured in a visual workflow builder without requiring developer involvement.

Q: Does automation reduce the need for finance headcount?

A: Automation typically doesn't reduce headcount — at least not directly. What it does is change what that headcount spends its time on. Finance teams that implement comprehensive automation consistently report shifting from 70% transactional processing to 70% analysis, advisory, and strategic support. For most CFOs, that's a far more valuable allocation of expensive human capital.