C560XL Captain reported finding a discrepancy between the AFM and the performance data from Dispatch and noted that the performance data provided on the release did not follow the FAR.

Narrative

We were departing ZZZ on a ferry flight. While reviewing the takeoff performance information for Runway XX departure procedure; I noticed something unusual. V1 was listed as 79 kt. This speed is below Vmcg and Vmca for the XLS. The remainder of the performance information looked reasonable. As a crew; we discussed the low V1 speed. We selected a revised V1 speed of 85 kt. based on our experience with performance calculations for the aircraft. Departure was uneventful.After the flight; I ran the performance using Genesis. The results I got from Genesis agreed exactly with the performance data on the flight release. I still had a feeling that the data was incorrect.Later; I got out the AFM and manually computed the takeoff performance using the conditions listed on the release. They differed substantially.Genesis data (V1/Vr/V2; Takeoff Field Length (TOFL)): 79/96/106; 4;704 ft.Hand-computed from the AFM (V1/Vr/V2; TOFL): 88/97/107; 5;350 ft.The AFM data I computed indicated V1 should have been 9 kt. faster than the release and the TOFL should have been 650 ft. longer than the release. The increased TOFL could impact obstacle clearance later in the takeoff flight path.The Dispatch performance and Genesis have always agreed in the past. I understood that they were both based on AFM performance data. However; in this case the Dispatch performance and Genesis differed significantly from what I got from the AFM. If Dispatch and Genesis are based on something other that the AFM; pilots need to know what they are based on.V1 should always be greater that Vmcg and Vr should always be greater than Vmca (reference FAR 25.107).Suggestions: Determine if the performance provided on the release is correct. If it is not determine why it is incorrect and correct it. Otherwise; please educate me on how to use the AFM data to get something near the Dispatch data.