Track the week, automate the admin.
Your calls arrive from the calendar you keep, and each project carries its client. By Friday Well holds the hours, the rate and the client.
The week you worked, and what it bills
Your calls arrive from the calendar you keep, and each held block already names the project it belongs to. Well places them on the hours they happened, then reads the same week as one row per client.
app.wellapp.ai
WWellapp
Show me last week as a calendar
Ask anything or use / for commands...
To invoice, by client
Sample figures, shaped like the week surface and the roll-up under it. Well records no time of its own: the call is what a connected tool supplies, and the rate is yours.
The numbers a pay month sits inside
Pay is one line in a month that also carries cash, burn, bills and what customers still owe. Each card is a workflow you can run in a session, drawn with the answer it gives back.
Where the hours come from before you bill them
You already sit in the calls. Connect the tool that recorded them and Well has the day: when it ran, how long it ran, and who was on it. Name the project and the rate once, and the day ends as an invoice instead of a spreadsheet.
One graph, and the four kinds of tool that fill it
A payslip on its own says very little. Well reads it next to what your workspace already holds: the notes from the meetings around it, the mail and the drives it arrived through, the payroll tool that issued it, and the ledger and the bank where the money shows up.
Meetings and notes
Meeting notes arrive as notes, and the people and companies named in them arrive as records. That is the context a pay question gets read against.
Mail and the drives
A payslip usually arrives as an attachment, or as a file someone dropped in a shared drive. Well picks it up there and keeps it as a document, summarised, sitting on the month it belongs to.
Payroll tools
The payroll tool you already run, read for the people it pays and the companies behind them. What else it brings depends on the tool: some fill the invoices they issue, a payslip engine fills payslips and their lines. What each person is owed stays computed where it is computed today.
Accounting and banks
The accounting tool and the bank accounts: the entries already booked, the accounts they sit on, and the movements on the bank. Well reads them in, and this section claims nothing about writing back.
What a filing asks for first
A return asks you for identifiers, accounts and a month that is actually closed. Three of these cards are reads you can run in a session, drawn with the answer they give back; the fourth drives the close itself. None of them files anything, and the band below names the returns no skill produces.
Your own payslip, line by line, into the books
One payslip in, one balanced entry out. Every journal line carries the payslip line it came from and the side Well read on it: an earning, a deduction from your pay, or a charge your company owes on top. Employer charges are an expense of their own; employee deductions never are.
Sample figures, shaped like the payslip record and the entry it posts.
Nothing to map. Your payslip labels are already known.
A payslip posts on the labels it already carries: 57 French payslip labels and 14 US ones are known on day one. Each label is read as the payslip prints it, whatever the casing or the apostrophe. A label Well does not know is proposed, confirmed once by you, and every waiting line posts from then on.
Salaire de base
earning
Base salary
An earning. It debits an expense role; the earnings add up to gross pay, and what is left after the deductions credits wages payable.
Heures supplémentaires 25%
earning
Overtime at 25%
An earning. It debits an expense role; the earnings add up to gross pay, and what is left after the deductions credits wages payable.
Prélèvement à la source
employee deduction
Income tax withheld at source
An employee deduction. It credits a liability role; the gross line already carries the debit.
Mutuelle santé part salariale
employee deduction
Supplementary health cover, employee share
An employee deduction. It credits a liability role; the gross line already carries the debit.
Sécurité sociale maladie part patronale
employer charge
Health insurance, employer share
An employer charge. It debits an expense role and credits a liability role.
Versement mobilité
employer charge
Transport levy
An employer charge. It debits an expense role and credits a liability role.
One line it cannot place stops the payslip
Nothing posts half a payslip. The next month's payslip carries a label Well has never seen, so the whole payslip stops, names the reason and waits for you. It also stops on a missing net pay, a gross that does not add up to its lines, a line whose side it cannot tell, and a month that is already locked.
Sample rows, shaped like the payslips view.
Halted: unmapped_rubric
This payslip did not post. Confirm the label once, and every payslip that carries it posts from then on.
Whether a payslip goes through or stops, what happened is on record, a closed month stays closed, and what Well holds for you is readable from outside Well.
Source kept
Every attempt to post a payslip is recorded with the payslip, the reason and the time, and each journal line carries the label of the payslip line it came from.
Locked means locked
A payslip cannot post into a closed month. A corrected payslip landing on a closed month stops instead of rewriting it.
It halts with period_locked
Readable from outside
Your payslips and journal entries are yours to read through the records API and Well's MCP server today. A payroll-only export is not built.
A data processing agreement and a sub-processor list are published on this site.
Your accountant gets an entry already in the ledger, not a folder of PDFs
When the accountant asks for the payroll at the close, there is nothing to send. The entry is already in the ledger Well keeps, beside your bank lines and invoices, and close readiness flags the payslip that stopped, with its reason, before the accountant asks.
Without Well
- The payslip lands in your inbox and sits there.
- You key it into the wrong account, or into none.
- The accountant asks for it the week the month closes.
- The close waits on a PDF.
With Well
- The payslip is read the day it arrives.
- Each line posts on the meaning it carries, or the payslip stops with the reason.
- The entry sits beside the bank lines and the invoices of the same month, as a draft, validated when you close the month.
- A payslip that arrived but did not post shows as a gap in close readiness, with the reason, before the accountant asks.
Close the month and the period's entries, the payroll one included, come out as a file: a CSV in any country, or the FEC file when the workspace is French. A draft is not in the file. Validating the month is what puts it there.
Ask once, from Claude or from Well
Payroll sits beside the bank, the ledger and your invoices in one workspace, so one question reads across all four. The same question runs from a Well session or from the AI client you already have open, through Well's MCP server. The tools that answer only read, with the access you grant.
Did every payslip this year post?
- Payslips
- 8 this year, 7 in the ledger
- 8
- Ledger
- 7 entries sourced from a payslip
- 7
- Halt
- 1 payslip with no entry
- 1
Also from any AI client that speaks MCP
Sample figures, shaped like the payslips view. The answer is the sentence. The rows are why.
Hours are not in here
Well holds what a payroll tool produced, not what produced it. Keep your tracker for the hours and the invoices you bill from them.
Stays where it is
- Hours, timers and timesheets
- Projects, rates and budgets
- Shifts, absences and leave balances
- Pay runs and social declarations
- Time to invoice
Lands in Well
- Payslips
- Payslip lines, with the hours when the payslip prints them
- Employment contracts, with their salary when the source carries it
- The ledger entries they post
- A timesheet, filed as a document you can read back
Questions a solo founder actually asks
What happens when it does not know a line?
The whole payslip stops, with the reason, and nothing posts until you confirm the label once. From then on every payslip that carries it posts. It also stops on a missing net pay, a gross that does not add up to its lines, a line whose side it cannot tell, and a month that is already locked.
I pay myself one payslip a month. Is this overkill?
One payslip is the case it was built for. Drop it, it posts to the ledger Well keeps for you, and the month can close without a second tool. Which pay channel your legal form requires is a question for your accountant: Well reads the payslip you were given, it does not infer the rule.
Does Well run payroll or file anything?
No. Your payroll tool computes the pay and files what goes with it. Well tells you what each payslip carried; it never files.
Which payroll tools connect today?
A payslip document from any tool, in any country. Deel and Deel (Token) are open under payroll and fill people, companies, invoices and transactions, never a payslip. No French payroll engine is connected; their payslips take the document path.
Does it read a French payslip, and a bulletin rectificatif?
Yes. 57 French payslip labels are known on day one, read as the payslip prints them, whatever the casing or the apostrophe. A corrected bulletin for the same month converges on the existing payslip: a payslip is keyed on the contract and the period, so it replaces the lines rather than adding a second payslip.
Where do my tracked hours go?
They stay in your tracker. Well has no timer, no projects and no rates. Hours reach Well only when a payslip line prints them, and a timesheet that arrives is filed as a document you can read back; Well does not count the hours in it.
What does my accountant see, and who else sees pay amounts?
Invite your accountant as a member and they read the same ledger: the payroll entry beside the bank lines and the invoices, as a draft until you close the month. Pay amounts are visible to every member of your workspace and of any workspace group it belongs to, not to a role, so decide who joins before a payslip does. Role-scoped visibility of pay amounts is not built.
What happens to my data if Well stops?
What Well holds for you is readable from outside Well today. The records API and Well's MCP server return your payslips, documents and journal entries. The same MCP server is what Claude, Cursor, Windsurf or ChatGPT read when you ask from there, with the access you grant. No MCP tool edits a payslip or a payslip line: the only MCP write that brings payroll in is a document upload, which takes the same path as a payslip you drop in. Moving the fiscal year start clears the draft entries of the workspace, the payroll one included, and the payslip then shows as a gap in close readiness. There is no payroll-only export.
Connect an AI clientDrop your last payslip and look
It becomes rows, the rows post, and a line Well cannot place is stopped, not guessed. Well is priced per seat: the Business plan is EUR 29 or USD 35 a month per seat, with no per-employee counter.