Skip to content
Pixel3S — Every process. Pixel-precise.

Finance & Accounting

Money moves when a named person confirms and a digital signature lands.

Pixel3S is the finance operations layer around ERP: payment request to payment order, approval memo by threshold, month-end close — with dual control, a digital signature, and a trail auditors can walk.

Request a walkthrough

Where it fails

  1. 01

    Confirmation lives in email. The payment order still posts. Nobody can say who owned the gate.

  2. 02

    Thresholds are a policy PDF. A high-value approval memo takes the short path when someone is in a hurry.

  3. 03

    The Chief Accountant and the signatory work from different packs. Version drift is treated as normal.

  4. 04

    Month-end close depends on a few people. Cycle time is a guess. Evidence is a compressed folder.

Confirm & sign

Three document families. Named owners at every gate.

A payment request, an approval memo, a month-end pack — each one leaves a trail of who confirmed, who signed, and when. ERP records the posting. Pixel3S records the path.
Payment request → payment order · PR-24091 · 85,000,000 ₫

Payment request → payment order

PR-24091 · 85,000,000 ₫

  1. Nguyễn A, Accountant: Draft the payment request
  2. Trần B, Reviewer: Check vendor, amount, cost center
  3. Phạm C, Chief Accountant: Confirm dual control
  4. Lê D, Signatory: Apply the digital signature
Approval memo — the path splits on amount · MEMO-0412 · 210,000,000 ₫

Approval memo — the path splits on amount

MEMO-0412 · 210,000,000 ₫

At or above threshold · ≥ 50,000,000 ₫

  1. Nguyễn A, Requester: Draft the approval memo
  2. Trần B, Manager: Confirm the content
  3. Phạm C, Chief Accountant: Confirm dual control
  4. Lê D, Signatory: Apply the digital signature

Below threshold

< 50,000,000 ₫

  1. Nguyễn A, Requester: Draft the approval memo
  2. Trần B, Manager: Confirm and release
Month-end close — checks, then sign-off · ME-2026-08

Month-end close — checks, then sign-off

ME-2026-08

  1. AP: Accounts payable cleared
  2. AR: Accounts receivable aged
  3. INV: Inventory cut-off done
  4. ACC: Accruals posted
  5. Phạm C, Chief Accountant: Confirm the close pack
  6. Lê D, CFO: Sign the month-end pack

3S applied

Systemize

Map request-to-pay and close-to-sign: intake, confirm gates, signatory, and the evidence required at each step.

Standardize

One path per document family, with named exceptions and an owner who can close the gate.

Synchronize

Vendor, cost center, signatory, and threshold masters stay common across the queues that use them.

Layers in play

Platform

Workflows · confirm & sign

Gates from payment request to payment order to digital signature, so work moves without chasing inboxes.

Workflows · confirm & sign

Platform

Process & SOP

The confirmation matrix: who confirms, who signs, at which threshold — versioned and owned.

Process & SOP

Platform

Control tower

A live finance queue: awaiting confirm, awaiting sign, signed today — built for the Chief Accountant and the controller, not for a presentation.

Control tower

Platform

Master data

Align vendor, cost center, signatory, and threshold so every queue speaks the same language.

Master data

Platform

Digital migration

Map document families as they run, cut over in windows, and stabilize.

Digital migration

Cutover

Pick one document family — payment request and payment order, approval memo, or month-end — on one entity. Run both paths through one period close, then retire the inbox path.

Request a walkthrough