Does Slipsheet support Microsoft Entra ID SSO?

Yes. Slipsheet signs in via Microsoft Entra ID with standard admin consent flows.

What permissions does Slipsheet request?

Only scoped file permissions via Microsoft Graph. No mailbox, calendar, or directory access is requested.

Can receipts land in a SharePoint document library?

Yes. Workbooks in OneDrive, SharePoint libraries, and Teams-backed SharePoint all work. Library permissions are respected.

Is data stored in the Microsoft tenant?

Extracted data is stored by Slipsheet; workbook rows live in your Microsoft tenant. Both are exportable and deletable.

Can multiple team members submit receipts to one workbook?

Yes. Multiple users can submit; each row records the submitter and requires approval before landing in the shared workbook.

How does this compare to full T&E platforms like Concur?

Slipsheet focuses on extraction and workbook sync, without travel booking, card feeds, or policy engines. Lighter than full T&E platforms for M365-native teams.

Sync Receipts to Microsoft 365

Date	Vendor	Total
APR 17	Contoso Logistics	$128.40
APR 15	Delta Airlines	$412.10
APR 14	Hertz Rental	$188.66
APR 12	Panera Bread	$14.72

§ 01 — The Method

One stack. One workflow.

Sign in with your Microsoft 365 account, scope access to the workbooks finance actually uses, and let extracted receipts flow into the close-the-books process you already run.

01 Step 1

Sign in with Entra ID.

Single sign-on via Microsoft Entra ID (formerly Azure AD). Tenant admins can review and approve Slipsheet's OAuth scopes through the standard app consent flow.

Auth · Entra ID · SSO

02 Step 2

Point to your team's workbooks.

Whether finance keeps expense trackers in OneDrive or a shared SharePoint library, point Slipsheet at the right file and worksheet. Scoped to that file only.

Sources · OneDrive · SharePoint

03 Step 3

Team submits, finance sees rows.

Anyone on the team can upload or forward receipts. After a confirmer approves them, rows land in the shared workbook finance opens every Monday.

Role-based · Approve · Sync

§ 02 — What syncs

Every field, itemised.

Every column your finance team expects at month-end — typed correctly, linked back to originals, audit-friendly.

№

Column

What lands in the sheet

Source

01

Date

Real date values for filtering, sorting, and fiscal-period grouping.

Extracted

02

Vendor

Normalized merchant name, consistent across submissions.

Extracted

03

Built for the Microsoft 365 shop.

Case · 01

Finance teams on M365.

Excel is the close process. SharePoint is the library. Slipsheet just feeds rows into the sheet the controller already opens on Monday morning.

Case · 02

Distributed teams with field expenses.

Reps on the road forward receipts from Outlook, managers approve, finance sees a clean feed. Entra ID ties submitter identity to every row.

Case · 03

Small & mid-market businesses.

No need for a heavyweight T&E platform. Microsoft 365 plus Slipsheet covers submission, review, and workbook-level reporting without a new seat fee per employee.

§ 04 — The old way vs. Slipsheet

Put down the data entry.

Manual data entry

Running M365 without receipt automation.

✗ Employees email receipts to a shared mailbox. Someone has to read them.
✗ Manual data entry into the expense tracker on SharePoint — every line.
✗ Receipts attached to emails get lost; workbook has no links back.
✗ Month-end close takes a day longer than it should.
✗ Auditor asks for original receipts; half of them are in people's inboxes.

Slipsheet + Microsoft 365

M365 plus a receipt pipeline.

✓ Employees upload or forward receipts — Slipsheet handles them.
✓ Extraction runs automatically; reviewers confirm in a keyboard-first queue.
✓ Rows append to your M365 Excel workbook with originals linked.
✓ Month-end close runs on the same data, without the data-entry day.
✓ Audit trail: every row links to the original file, with submitter attached.

§ 05 — Questions, answered

The fine print.

Yes. Sign-in goes through Microsoft Entra ID (formerly Azure AD). Tenant admins can review the requested OAuth scopes and grant admin consent org-wide, or let individual users consent.

Only what's needed to read and write the specific workbooks you authorize — scoped file access via Microsoft Graph. Slipsheet does not request mailbox, calendar, or directory scopes.

Yes. Target any workbook your account can write to — OneDrive, SharePoint site libraries, or Teams-backed SharePoint. Existing library permissions still apply.

Receipt files and the extracted ledger are stored in Slipsheet's infrastructure. Workbook rows live in your tenant's OneDrive/SharePoint. You can export or delete either side at any time.

Yes. Each submitter connects their own Microsoft account, and every row records who uploaded it. Approval workflows ensure only confirmed receipts land in the shared workbook.

Slipsheet is deliberately smaller. We extract receipts and write rows to your Excel workbook — that's it. If your team already lives in M365 and you don't need travel booking, card feeds, or policy engines, Slipsheet is the lighter lift.

§ 06 — Your turn

Plug it in.
Close on time.

14 days. No card. No new seat licenses. Microsoft 365 keeps doing what it does; Slipsheet handles the receipts nobody wanted to type.

Open your ledger Already a filer? Sign in