How PEQY works

PEQY reviews every AL pull request: it resolves Business Central symbols, verifies its findings against the AL compiler, and only speaks when it can back up what it says. The review sees the whole repository and its symbols as context, reviewing the change against them instead of the diff alone.

Submit your PR in Git

Open a pull request on GitHub, GitLab or Azure DevOps. PEQY picks it up automatically. No change to your process. When a work item or issue is linked, PEQY reads it and flags changes that do not match the requirements.

Invisible checks

PEQY doesn't get in your way. We only notify you when it's important.

3412 checks passed

1 check failed

2 suggestions

Suggestion

Posting date not validated before ledger entry

The new PostBatch procedure inserts G/L entries without validating "Posting Date" against the allowed posting range. A batch dated into a closed period posts...

Suggested fix

Validate "Posting Date" against the allowed posting range from General Ledger Setup (Allow Posting From/To) before inserting, and fail with a clear error message when the date falls outside it, mirroring the standard GenJnlCheckLine behavior.

PEQY is great from day one, and grounded in your standards.

Built on the Business Central symbol model and a research-led review taxonomy, extended with custom rules for your team's standards.

Our Research

Our research database informs how PEQY is built and evaluated: quantitative and qualitative research led by devs, not LLMs.

Your standards

Custom review rules per repository put your team's conventions right next to PEQY's built-in AL review; you decide what gets enforced.

Find out more about our research

Built into your pull request workflow.

PEQY automatically runs on every pull request and surfaces results directly in GitHub, GitLab and Azure DevOps, including on-premises Azure DevOps Server.

GitHub

GitLab

Azure DevOps