Receipt capture
Partly covered
Photograph or forward a receipt and the app reads the merchant, date, and amount.
Why it matters. Cuts out typing expense lines by hand.
On Borg. Receipts can be photographed and attached; automatic field reading depends on a self-hosted OCR step rather than a built-in service.
Approval workflows
Planned
An expense routes to a manager or finance for sign-off before it's paid.
Why it matters. Keeps spending inside policy without a manual review queue.
On Borg. The open-source App repo is a client for Expensify's own hosted backend; there's no evidence Borg runs an independent backend, so chat-based approval routing needs that hosted service to work.
Corporate card management
Planned
Issue cards, set limits, and reconcile card transactions automatically.
Why it matters. Removes manual matching of card statements to receipts.
On Borg. Not available; card issuing and bank-grade transaction feeds are tied to a card program a self-hosted deployment doesn't have.
Reimbursement (ACH)
Planned
Send an approved reimbursement straight to an employee's bank account.
Why it matters. Avoids a manual payroll add-on or a paper check run.
On Borg. Not built in; a self-hosted deployment needs its own banking or ACH processor to move money.
Push coded expenses into
QuickBooks,
Xero, NetSuite, or Sage Intacct.
Why it matters. Keeps the general ledger current without double entry.
On Borg.
QuickBooks/
Xero connector code exists in the repo, but it runs against Expensify's hosted backend; API credentials alone don't give Borg's self-hosted deployment an independent sync path.
Spend reporting
Partly covered
Dashboards break spend down by category, project, or employee.
Why it matters. Gives finance visibility before a month-end surprise.
On Borg. Reporting views exist in the open-source client, but they read expense data from Expensify's hosted backend rather than an independent Borg-run service.
Some upstream apps gate certain features behind their own licenses; the coverage chips above say where.