BE-400 Captain reported receiving an ATC low altitude alert while on final approach in visual conditions. The Captain leveled the descent regaining the proper descent profile; and landed safely.

Narrative

On Day 0; around XA:15; I was Pilot Flying (and Pilot In Command) for a visual approach into ZZZ; Runway XX. Visual conditions prevailed. After getting cleared for the visual approach and switching to Tower from local approach control; the vector to intercept the final approach course (116 degrees) was closer to the final approach fix (ZZZ) RNAV XX approach input into the FMS; for the aircraft's navigation computer to compute a vertical guidance down to the TDZE with a 3.0 degree glidepath. Knowing this from previous experience; I elected to switch off autopilot and hand fly down to the runway without the use of the Flight Director. Given the flat conditions and lack of obvious surrounding terrain information; I inadvertently flew lower than anticipated and continued homing to the runway searching for the PAPIs for vertical guidance. At some point; I realized I got a little too low on the visual approach and was still searching for the PAPIs. Simultaneously; ZZZ Tower informed me of a low altitude alert; and I halted descent (leveling off) and coasted to about 1-2 nm from the runway before visually picking up the PAPIs. At that point; I was able to land uneventfully. I was not issued a violation or given a phone number to call but I was aware that I got about 100-200 feet below glidepath before realizing I was lower than the prescribed RNAV XX approach into ZZZ. In future; I will be sure to use the aircraft's visual approach FMS settings for the runway because the aircraft's navigation computer is better able to compute vertical guidance when vectoring close to the final approach fix (or pilot designated fix whether that is 3-5 miles out) and still provide a flight director for vertical guidance down to the runway.