Custom SQL reports allow you to extract personalised data from your Factorial account in a very specific format. To make sure we can deliver exactly what you need as quickly as possible, this article explains:
- What information you should include when requesting a report
- How the SQL request process works
- What “Solved” means
- What to do if the data is wrong or you need changes
Before you start: what is an SQL report?
An SQL report is a custom-built table created especially for you by our technical team.
It is not a standard export or widget — it is tailored to your exact needs.
Because of this, we need very clear information to make sure your report is accurate.
1. What to Include When Requesting an SQL Report
When you open a ticket to request an SQL report, please make sure it is opened under:
Click here to request a report (SQL) (One SQL request per ticket).
a. What information do you want?
Tell us exactly what data you need.
Example:
- Overtime hours
- Time off taken per month
- Headcount list
- Costs per employee
- Sales or performance data
The clearer, the better.
b. What will the report be used for?
This helps us understand the context and ensures that the structure matches your goal.
Examples:
- Monthly reporting
- Budgeting
- Audits
- Internal analysis
c. What should the final table look like?
If you can, include:
- A sample table
- A screenshot
- Or a list of the columns in order
d. Detailed information for each column
For every column you need, please provide:
- Column name
- What it represents
- Where the data comes from inside Factorial
- Formula used (only if the value must be calculated)
Example: Time Off reports
If your report concerns time off, please confirm:
- Which absence types to include or exclude
- The exact absence names as they appear in Factorial
- Working days configured in contract and in Time Planning
2. What Happens After You Submit the Request?
Once you send your ticket, your SQL request goes through three phases.
Here’s what each one means:
Phase 1. SQL Review
A specialist reviews your request to check:
- Is all the required information provided?
- Is the report feasible?
- Do we need clarification?
If information is missing, we will return the request to you and ask for the missing details.
First response SLA: 4 working hours
If your request can be covered by a custom widget, we will let you know before continuing.
Phase 2. SQL Scheduled
Once everything is clear and confirmed:
- We schedule your report
- An SQL Implementer starts building it
Delivery SLA: 7 working days (45 working hours)
The SQL will be delivered directly inside your Factorial account.
Phase 3. Solved
When your report is ready, the ticket moves to “Solved”.
What “Solved” means:
- Your report is ready
- You now have 5 days to check the data
- You can still report mistakes — we will reopen the ticket
What “Solved” does not mean:
- It does NOT mean the request is closed forever.
- It simply means the report has been delivered and is waiting for your confirmation.
3. What if something is wrong?
You have up to 5 days to review the data.
If the data is incorrect:
- Reply to the ticket
- Explain what is wrong
- Provide an example of the incorrect value
- We will reopen the ticket and fix it
- The issue will go back to the SQL Scheduled phase
4. What if you need more data later on?
If your report is correct, but you now need:
- new columns
- new filters
- new formulas
- a modified table structure
Please open a new SQL request here.
This helps keep each modification properly tracked and ensures a smooth process.